Model predictive maintenance system with incentive incorporation

ABSTRACT

A model predictive maintenance system for building equipment including an equipment controller to operate the building equipment to affect a variable state or condition in a building. The system includes an operational cost predictor to predict a cost of operating the building equipment over a duration of an optimization period, a maintenance cost predictor to predict a cost of performing maintenance on the building equipment, and a cost incentive manager to determine whether any cost incentives are available and, in response to a determination that cost incentives are available, identify the cost incentives. The system includes an objective function optimizer to optimize an objective function to predict a total cost associated with the building equipment over the duration of the optimization period. The objective function includes the predicted cost of operating the building equipment, the predicted cost of performing maintenance on the building equipment, and, if available, the cost incentives.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 15/895,836 filed Feb. 13, 2018, which claims the benefit of and priority to U.S. Provisional Patent Application No. 62/511,113 filed May 25, 2017. The entire contents of both these patent applications are incorporated herein by reference.

BACKGROUND

The present disclosure relates generally to a maintenance system for building equipment and more particularly to a maintenance system that uses a predictive optimization technique to determine an optimal maintenance strategy for the building equipment.

Building equipment is typically maintained according to a maintenance strategy for the building equipment. One type of maintenance strategy is run-to-fail. The run-to-fail strategy allows the building equipment to run until a failure occurs. During this running period, only minor operational maintenance tasks (e.g., oil changes) are performed to maintain the building equipment.

Another type of maintenance strategy is preventative maintenance. The preventative maintenance strategy typically involves performing a set of preventative maintenance tasks recommended by the equipment manufactured. The preventative maintenance tasks are usually performed at regular intervals (e.g., every month, every year, etc.) which may be a function of the elapsed time of operation and/or the run hours of the building equipment.

SUMMARY

One implementation of the present disclosure is a model predictive maintenance system for building equipment, according to some embodiments. The model predictive maintenance system includes an equipment controller configured to operate the building equipment to affect a variable state or condition in a building, according to some embodiments. The model predictive maintenance system includes an operational cost predictor configured to predict a cost of operating the building equipment over a duration of an optimization period, according to some embodiments. The model predictive maintenance system includes a maintenance cost predictor configured to predict a cost of performing maintenance on the building equipment over the duration of the optimization period, according to some embodiments. The model predictive maintenance system includes a cost incentive manager configured to determine whether any cost incentives are available, according to some embodiments. The cost incentive manager is configured to, in response to a determination that one or more cost incentives are available, identify the one or more cost incentives associated with performing maintenance on the building equipment, according to some embodiments. The model predictive maintenance system includes an objective function optimizer configured to optimize an objective function to predict a total cost associated with the building equipment over the duration of the optimization period, according to some embodiments. The objective function includes the predicted cost of operating the building equipment, the predicted cost of performing maintenance on the building equipment, and, in response to a determination that the one or more cost incentives are available, the one or more cost incentives associated with performing maintenance on the building equipment, according to some embodiments.

In some embodiments, the model predictive maintenance system includes a capital cost predictor configured to predict a cost of purchasing or replacing the building equipment over the duration of the optimization period. The objective function includes the predicted cost of purchasing or replacing the building equipment, according to some embodiments.

In some embodiments, the cost incentive manager is configured to determine one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.

In some embodiments, the model predictive maintenance system includes an objective function generator configured to dynamically update the objective function on a real-time basis based on closed-loop feedback from the building equipment.

In some embodiments, the costive incentive manager is configured to identify a time period for each of the one or more cost incentives when each of the one or more cost incentives are available. The objective function further includes the time period for each of the one or more cost incentives, according to some embodiments.

In some embodiments, the one or more cost incentives each define one or more requirements to achieve the cost incentive.

In some embodiments, the objective function optimizer is configured to determine an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives. The objective function optimizer is configured to optimize the objective function to determine whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith, according to some embodiments. Optimizing the objective function includes minimizing the predicted total cost over the duration of the optimization period, according to some embodiments.

Another implementation of the present disclosure is a method for performing model predictive maintenance for building equipment, according to some embodiments. The method includes operating the building equipment to affect a variable state or condition in a building, according to some embodiments. The method includes predicting a cost of operating the building equipment over a duration of an optimization period, according to some embodiments. The method includes predicting a cost of performing maintenance on the building equipment over the duration of the optimization period, according to some embodiments. The method includes determining whether any cost incentives are available, according to some embodiments. The method includes, in response to a determination that one or more cost incentives are available, identifying the one or more cost incentives associated with performing a maintenance on the building equipment, according to some embodiments. The method includes optimizing an objective function to predict a total cost associated with the building equipment over the duration of the optimization period, according to some embodiments. The objective function includes the predicted cost of operating the building equipment, the predicted cost of performing maintenance on the building equipment, and, in response to a determination that the one or more cost incentives are available, the one or more cost incentives associated with performing maintenance on the building equipment, according to some embodiments.

In some embodiments, the method includes predicting a cost of purchasing or replacing the building equipment over the duration of the optimization period. The objective function includes the predicted cost of purchasing or replacing the building equipment, according to some embodiments.

In some embodiments, the method includes determining one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.

In some embodiments, optimizing the objective function includes minimizing the objective function to determine whether and when to perform each particular type of maintenance to minimize the total cost associated with the building equipment over the duration of the optimization period

In some embodiments, the one or more cost incentives each define one or more requirements to achieve the cost incentive.

In some embodiments, the method includes determining an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives. Optimizing the objective function includes determining whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith, according to some embodiments. Optimizing the objective function includes minimizing the predicted total cost over the duration of the optimization period, according to some embodiments.

Another implementation of the present disclosure is a model predictive maintenance system for building equipment, according to some embodiments. The model predictive maintenance system includes an equipment controller configured to operate the building equipment to affect a variable state or condition in a building, according to some embodiments. The model predictive maintenance system includes an operational cost predictor configured to predict a cost of operating the building equipment over a duration of an optimization period, according to some embodiments. The model predictive maintenance system includes a maintenance cost predictor configured to predict a cost of performing maintenance on the building equipment over the duration of the optimization period, according to some embodiments. The model predictive maintenance system includes a cost incentive manager configured to determine whether any cost incentives are available, according to some embodiments. The cost incentive manager is configured to, in response to a determination that one or more cost incentives are available, identify the one or more cost incentives associated with performing maintenance on the building equipment, according to some embodiments. The model predictive maintenance system includes an objective function optimizer configured to optimize an objective function to determine an optimal strategy for operating and maintaining the building equipment over the duration of the optimization period, according to some embodiments. The objective function includes the predicted cost of operating the building equipment, the predicted cost of performing maintenance on the building equipment, and, in response to a determination that the one or more cost incentives are available, the one or more cost incentives associated with performing maintenance on the building equipment, according to some embodiments.

In some embodiments, the model predictive maintenance system includes a capital cost predictor configured to predict a cost of purchasing or replacing the building equipment over the duration of the optimization period. The objective function includes the predicted cost of purchasing or replacing the building equipment, according to some embodiments.

In some embodiments, the cost incentive manager is configured to determine one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.

In some embodiments, the model predictive maintenance system includes an objective function generator configured to dynamically update the objective function on a real-time basis based on closed-loop feedback from the building equipment.

In some embodiments, the cost incentive manager is configured to identify a time period for each of the one or more cost incentives when each of the one or more cost incentives are available. The objective function further includes the time period for each of the one or more cost incentives, according to some embodiments.

In some embodiments, the one or more cost incentives each define one or more requirements to achieve the cost incentive.

In some embodiments, the objective function optimizer is configured to determine an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives. The objective function optimizer is configured to optimize the objective function to determine whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith, according to some embodiments. Optimizing the objective function includes minimizing the predicted total cost over the duration of the optimization period, according to some embodiments.

Those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices and/or processes described herein, as defined solely by the claims, will become apparent in the detailed description set forth herein and taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing of a building equipped with a HVAC system, according to some embodiments.

FIG. 2 is a block diagram of a waterside system which can be used to serve the heating or cooling loads of the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system which can be used to serve the heating or cooling loads of the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) which can be used to monitor and control the building of FIG. 1, according to some embodiments.

FIG. 5 is a block diagram of another BMS which can be used to monitor and control the building of FIG. 1, according to some embodiments.

FIG. 6 is a block diagram of a building system including a model predictive maintenance (MPM) system that monitors equipment performance information from connected equipment installed in the building, according to some embodiments.

FIG. 7 is a schematic diagram of a chiller which may be a type of connected equipment that provides equipment performance information to the MPM system of FIG. 6, according to some embodiments.

FIG. 8 is a block diagram illustrating the MPM system of FIG. 6 in greater detail, according to some embodiments.

FIG. 9 is a block diagram illustrating a high level optimizer of the MPM system of FIG. 6 in greater detail, according to some embodiments.

FIG. 10 is a flowchart of a process for operating the MPM system of FIG. 6, according to some embodiments.

FIG. 11 is a graph illustrating degradation and average power consumption of building equipment over time, according to some embodiments.

FIG. 12 is a graph illustrating failure rate of building equipment over time, according to some embodiments.

FIG. 13 is a graph illustrating functional performance of building equipment over time, according to some embodiments.

FIG. 14 is a graph illustrating cumulative maintenance expenditures over time with a cost incentive, according to some embodiments.

FIG. 15 is a block diagram illustrating the MPM system of FIG. 6 in greater detail, according to some embodiments.

FIG. 16 is a block diagram illustrating the high level optimizer of FIG. 15 in greater detail, according to some embodiments.

FIG. 17 is a flow diagram of a process for optimizing an objective function given cost incentive information, according to some embodiments.

FIGS. 18A-18B are drawings of a variable refrigerant flow (VRF) system having one or more outdoor VRF units and a plurality of indoor VRF units, according to some embodiments.

DETAILED DESCRIPTION

Overview

Referring generally to the FIGURES, a model predictive maintenance (MPM) system and components thereof are shown, according to various exemplary embodiments. The MPM system can be configured to determine an optimal maintenance strategy for building equipment. In some embodiments, the optimal maintenance strategy is a set of decisions which optimizes the total cost associated with purchasing, maintaining, and operating the building equipment over the duration of an optimization period (e.g., 30 weeks, 52 weeks, 10 years, 30 years, etc.). The decisions can include, for example, equipment purchase decisions, equipment maintenance decisions, and equipment operating decisions. The MPM system can use a model predictive control technique to formulate an objective function which expresses the total cost as a function of these decisions, which can be included as decision variables in the objective function. The MPM system can optimize (e.g., minimize) the objective function using any of a variety of optimization techniques to identify the optimal values for each of the decision variables.

One example of an objective function which can be optimized by The MPM system is shown in the following equation:

$J = {{\sum\limits_{i = 1}^{h}\;{C_{{op},i}P_{{op},i}\Delta\; t}} + {\sum\limits_{i = 1}^{h}\;{C_{{main},i}B_{{main},i}}} + {\sum\limits_{i = 1}^{h}\;{C_{{cap},i}P_{{cap},i}}}}$ where C_(op,i) is the cost per unit of energy (e.g., $/kWh) consumed by the building equipment at time step i of the optimization period, P_(op,i) is the power consumption (e.g., kW) of the building equipment at time step i, Δt is the duration of each time step i, C_(main,i) is the cost of maintenance performed on the building equipment at time step i, B_(main,i) is a binary variable that indicates whether the maintenance is performed, C_(cap,i) is the capital cost of purchasing a new device of the building equipment at time step i, B_(cap,i) is a binary variable that indicates whether the new device is purchased, and h is the duration of the horizon or optimization period over which the optimization is performed.

The first term in the objective function J represents the operating cost of the building equipment over the duration of the optimization period. In some embodiments, the cost per unit of energy C_(op,i) is received from a utility as energy pricing data. The cost C_(op,i) may be a time-varying cost that depends on the time of day, the day of the week (e.g., weekday vs. weekend), the current season (e.g., summer vs. winter), or other time-based factors. For example, the cost C_(op,i) may be higher during peak energy consumption periods and lower during off-peak or partial-peak energy consumption periods.

In some embodiments, the power consumption P_(op,i) is based on the heating or cooling load of the building. The heating or cooling load can be predicted by the MPM system as a function of building occupancy, the time of day, the day of the week, the current season, or other factors that can affect the heating or cooling load. In some embodiments, the MPM system uses weather forecasts from a weather service to predict the heating or cooling load. The power consumption P_(op,i) may also depend on the efficiency η_(i) of the building equipment. For example, building equipment that operate at a high efficiency may consume less power P_(op,i) to satisfy the same heating or cooling load relative to building equipment that operate at a low efficiency.

Advantageously, the MPM system can model the efficiency η_(i) of the building equipment at each time step i as a function of the maintenance decisions B_(main,i) and the equipment purchase decisions B_(cap,i). For example, the efficiency η_(i) for a particular device may start at an initial value η₀ when the device is purchased and may degrade over time such that the efficiency η_(i) decreases with each successive time step i. Performing maintenance on a device may reset the efficiency η_(i) to a higher value immediately after the maintenance is performed. Similarly, purchasing a new device to replace an existing device may reset the efficiency η_(i) to a higher value immediately after the new device is purchased. After being reset, the efficiency η_(i) may continue to degrade over time until the next time at which maintenance is performed or a new device is purchased.

Performing maintenance or purchasing a new device may result in a relatively lower power consumption P_(op,i) during operation and therefore a lower operating cost at each time step i after the maintenance is performed or the new device is purchased. In other words, performing maintenance or purchasing a new device may decrease the operating cost represented by the first term of the objective function J. However, performing maintenance may increase the second term of the objective function J and purchasing a new device may increase the third term of the objective function J. The objective function J captures each of these costs and can be optimized by the MPM system to determine the optimal set of maintenance and equipment purchase decisions (i.e., optimal values for the binary decision variables B_(main,i) and B_(cap,i)) over the duration of the optimization period.

In some embodiments, the MPM system uses equipment performance information received as a feedback from the building equipment to estimate the efficiency and/or the reliability of the building equipment. The efficiency may indicate a relationship between the heating or cooling load on the building equipment and the power consumption of the building equipment. The MPM system can use the efficiency to calculate the corresponding value of P_(op,i). The reliability may be a statistical measure of the likelihood that the building equipment will continue operating without fault under its current operating conditions. Operating under more strenuous conditions (e.g., high load, high temperatures, etc.) may result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) may result in a higher reliability. In some embodiments, the reliability is based on an amount of time that has elapsed since the building equipment last received maintenance and/or an amount of time that has elapsed since the building equipment was purchased or installed.

In some embodiments, the MPM system generates and provides equipment purchase and maintenance recommendations. The equipment purchase and maintenance recommendations may be based on the optimal values for the binary decision variables B_(main,i) and B_(cap,i) determined by optimizing the objective function J. For example, a value of B_(main,25)=1 for a particular device of the building equipment may indicate that maintenance should be performed on that device at the 25^(th) time step of the optimization period, whereas a value of B_(main,25)=0 may indicate that the maintenance should not be performed at that time step. Similarly, a value of B_(cap,25)=1 may indicate that a new device of the building equipment should be purchased at the 25^(th) time step of the optimization period, whereas a value of B_(cap,25)=0 may indicate that the new device should not be purchased at that time step.

Advantageously, the equipment purchase and maintenance recommendations generated by the MPM system are predictive recommendations based on the actual operating conditions and actual performance of the building equipment. The optimization performed by the MPM system weighs the cost of performing maintenance and the cost of purchasing new equipment against the decrease in operating cost resulting from such maintenance or purchase decisions in order to determine the optimal maintenance strategy that minimizes the total combined cost. In this way, the equipment purchase and maintenance recommendations generated by the MPM system may be specific to each group of building equipment in order to achieve the optimal cost J for that specific group of building equipment. The equipment-specific recommendations may result in a lower overall cost J relative to generic preventative maintenance recommendations provided by an equipment manufacturer (e.g., service equipment every year) which may be sub-optimal for some groups of building equipment and/or some operating conditions. These and other features of the MPM system are described in detail below.

Building HVAC Systems and Building Management Systems

Referring now to FIGS. 1-5, several building management systems (BMS) and HVAC systems in which the systems and methods of the present disclosure can be implemented are shown, according to some embodiments. In brief overview, FIG. 1 shows a building 10 equipped with a HVAC system 100. FIG. 2 is a block diagram of a waterside system 200 which can be used to serve building 10. FIG. 3 is a block diagram of an airside system 300 which can be used to serve building 10. FIG. 4 is a block diagram of a BMS which can be used to monitor and control building 10. FIG. 5 is a block diagram of another BMS which can be used to monitor and control building 10.

Building and HVAC System

Referring particularly to FIG. 1, a perspective view of a building 10 is shown. Building 10 is served by a BMS. A BMS is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof.

The BMS that serves building 10 includes a HVAC system 100. HVAC system 100 can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 may provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 may use the heated or chilled fluid to heat or cool an airflow provided to building 10. An exemplary waterside system and airside system which can be used in HVAC system 100 are described in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 may use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 can be located in or around building 10 (as shown in FIG. 1) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid can be heated in boiler 104 or cooled in chiller 102, depending on whether heating or cooling is required in building 10. Boiler 104 may add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller 102 may place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 can be transported to AHU 106 via piping 108.

AHU 106 may place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 may transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid may then return to chiller 102 or boiler 104 via piping 110.

Airside system 130 may deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and may provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 may receive input from sensors located within AHU 106 and/or within the building zone and may adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

Referring now to FIG. 2, a block diagram of a waterside system 200 is shown, according to some embodiments. In various embodiments, waterside system 200 may supplement or replace waterside system 120 in HVAC system 100 or can be implemented separate from HVAC system 100. When implemented in HVAC system 100, waterside system 200 can include a subset of the HVAC devices in HVAC system 100 (e.g., boiler 104, chiller 102, pumps, valves, etc.) and may operate to supply a heated or chilled fluid to AHU 106. The HVAC devices of waterside system 200 can be located within building 10 (e.g., as components of waterside system 120) or at an offsite location such as a central plant.

In FIG. 2, waterside system 200 is shown as a central plant having a plurality of subplants 202-212. Subplants 202-212 are shown to include a heater subplant 202, a heat recovery chiller subplant 204, a chiller subplant 206, a cooling tower subplant 208, a hot thermal energy storage (TES) subplant 210, and a cold thermal energy storage (TES) subplant 212. Subplants 202-212 consume resources (e.g., water, natural gas, electricity, etc.) from utilities to serve thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example, heater subplant 202 can be configured to heat water in a hot water loop 214 that circulates the hot water between heater subplant 202 and building 10. Chiller subplant 206 can be configured to chill water in a cold water loop 216 that circulates the cold water between chiller subplant 206 building 10. Heat recovery chiller subplant 204 can be configured to transfer heat from cold water loop 216 to hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop 218 may absorb heat from the cold water in chiller subplant 206 and reject the absorbed heat in cooling tower subplant 208 or transfer the absorbed heat to hot water loop 214. Hot TES subplant 210 and cold TES subplant 212 may store hot and cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building 10 to serve thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.

Although subplants 202-212 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) can be used in place of or in addition to water to serve thermal energy loads. In other embodiments, subplants 202-212 may provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system 200 are within the teachings of the present disclosure.

Each of subplants 202-212 can include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configured to store the hot water for later use. Hot TES subplant 210 may also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242. Cold TES subplant 212 is shown to include cold TES tanks 244 configured to store the cold water for later use. Cold TES subplant 212 may also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in waterside system 200 include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system 200. In various embodiments, waterside system 200 can include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system 200 and the types of loads served by waterside system 200.

Airside System

Referring now to FIG. 3, a block diagram of an airside system 300 is shown, according to some embodiments. In various embodiments, airside system 300 may supplement or replace airside system 130 in HVAC system 100 or can be implemented separate from HVAC system 100. When implemented in HVAC system 100, airside system 300 can include a subset of the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers, etc.) and can be located in or around building 10. Airside system 300 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by waterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type air handling unit (AHU) 302. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 302 may receive return air 304 from building zone 306 via return air duct 308 and may deliver supply air 310 to building zone 306 via supply air duct 312. In some embodiments, AHU 302 is a rooftop unit located on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1) or otherwise positioned to receive both return air 304 and outside air 314. AHU 302 can be configured to operate exhaust air damper 316, mixing damper 318, and outside air damper 320 to control an amount of outside air 314 and return air 304 that combine to form supply air 310. Any return air 304 that does not pass through mixing damper 318 can be exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 can be operated by an actuator. For example, exhaust air damper 316 can be operated by actuator 324, mixing damper 318 can be operated by actuator 326, and outside air damper 320 can be operated by actuator 328. Actuators 324-328 may communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 may receive control signals from AHU controller 330 and may provide feedback signals to AHU controller 330. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators 324-328. AHU controller 330 can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil 334, a heating coil 336, and a fan 338 positioned within supply air duct 312. Fan 338 can be configured to force supply air 310 through cooling coil 334 and/or heating coil 336 and provide supply air 310 to building zone 306. AHU controller 330 may communicate with fan 338 via communications link 340 to control a flow rate of supply air 310. In some embodiments, AHU controller 330 controls an amount of heating or cooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200 (e.g., from cold water loop 216) via piping 342 and may return the chilled fluid to waterside system 200 via piping 344. Valve 346 can be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200 (e.g., from hot water loop 214) via piping 348 and may return the heated fluid to waterside system 200 via piping 350. Valve 352 can be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.

Each of valves 346 and 352 can be controlled by an actuator. For example, valve 346 can be controlled by actuator 354 and valve 352 can be controlled by actuator 356. Actuators 354-356 may communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 may receive control signals from AHU controller 330 and may provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 may also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a setpoint temperature for supply air 310 or to maintain the temperature of supply air 310 within a setpoint temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU 330 may control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include a building management system (BMS) controller 366 and a client device 368. BMS controller 366 can include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for airside system 300, waterside system 200, HVAC system 100, and/or other controllable systems that serve building 10. BMS controller 366 may communicate with multiple downstream building systems or subsystems (e.g., HVAC system 100, a security system, a lighting system, waterside system 200, etc.) via a communications link 370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMS controller 366 can be separate (as shown in FIG. 3) or integrated. In an integrated implementation, AHU controller 330 can be a software module configured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 may provide BMS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.

Client device 368 can include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system 100, its subsystems, and/or devices. Client device 368 can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device 368 can be a stationary terminal or a mobile device. For example, client device 368 can be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 may communicate with BMS controller 366 and/or AHU controller 330 via communications link 372.

Building Management Systems

Referring now to FIG. 4, a block diagram of a building management system (BMS) 400 is shown, according to some embodiments. BMS 400 can be implemented in building 10 to automatically monitor and control various building functions. BMS 400 is shown to include BMS controller 366 and a plurality of building subsystems 428. Building subsystems 428 are shown to include a building electrical subsystem 434, an information communication technology (ICT) subsystem 436, a security subsystem 438, a HVAC subsystem 440, a lighting subsystem 442, a lift/escalators subsystem 432, and a fire safety subsystem 430. In various embodiments, building subsystems 428 can include fewer, additional, or alternative subsystems. For example, building subsystems 428 may also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy service subsystem, or any other type of building subsystem that uses controllable equipment and/or sensors to monitor or control building 10. In some embodiments, building subsystems 428 include waterside system 200 and/or airside system 300, as described with reference to FIGS. 2-3.

Each of building subsystems 428 can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 can include many of the same components as HVAC system 100, as described with reference to FIGS. 1-3. For example, HVAC subsystem 440 can include a chiller, a boiler, any number of air handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and other devices for controlling the temperature, humidity, airflow, or other variable conditions within building 10. Lighting subsystem 442 can include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices configured to controllably adjust the amount of light provided to a building space. Security subsystem 438 can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include a communications interface 407 and a BMS interface 409. Interface 407 may facilitate communications between BMS controller 366 and external applications (e.g., monitoring and reporting applications 422, enterprise control applications 426, remote systems and applications 444, applications residing on client devices 448, etc.) for allowing user control, monitoring, and adjustment to BMS controller 366 and/or subsystems 428. Interface 407 may also facilitate communications between BMS controller 366 and client devices 448. BMS interface 409 may facilitate communications between BMS controller 366 and building subsystems 428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems 428 or other external systems or devices. In various embodiments, communications via interfaces 407, 409 can be direct (e.g., local wired or wireless communications) or via a communications network 446 (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces 407, 409 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces 407, 409 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 409 can include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BMS interface 409 is an Ethernet interface. In other embodiments, both communications interface 407 and BMS interface 409 are Ethernet interfaces or are the same Ethernet interface.

Still referring to FIG. 4, BMS controller 366 is shown to include a processing circuit 404 including a processor 406 and memory 408. Processing circuit 404 can be communicably connected to BMS interface 409 and/or communications interface 407 such that processing circuit 404 and the various components thereof can send and receive data via interfaces 407, 409. Processor 406 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.

Memory 408 (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory 408 can be or include volatile memory or non-volatile memory. Memory 408 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to some embodiments, memory 408 is communicably connected to processor 406 via processing circuit 404 and includes computer code for executing (e.g., by processing circuit 404 and/or processor 406) one or more processes described herein.

In some embodiments, BMS controller 366 is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BMS controller 366 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while FIG. 4 shows applications 422 and 426 as existing outside of BMS controller 366, in some embodiments, applications 422 and 426 can be hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterprise integration layer 410, an automated measurement and validation (AM&V) layer 412, a demand response (DR) layer 414, a fault detection and diagnostics (FDD) layer 416, an integrated control layer 418, and a building subsystem integration later 420. Layers 410-420 can be configured to receive inputs from building subsystems 428 and other data sources, determine optimal control actions for building subsystems 428 based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems 428. The following paragraphs describe some of the general functions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 can be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications 426 can be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications 426 may also or alternatively be configured to provide configuration GUIs for configuring BMS controller 366. In yet other embodiments, enterprise control applications 426 can work with layers 410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 can be configured to manage communications between BMS controller 366 and building subsystems 428. For example, building subsystem integration layer 420 may receive sensor data and input signals from building subsystems 428 and provide output data and control signals to building subsystems 428. Building subsystem integration layer 420 may also be configured to manage communications between building subsystems 428. Building subsystem integration layer 420 translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.

Demand response layer 414 can be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of building 10. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems 424, from energy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demand response layer 414 may receive inputs from other layers of BMS controller 366 (e.g., building subsystem integration layer 420, integrated control layer 418, etc.). The inputs received from other layers can include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs may also include inputs such as electrical use (e.g., expressed in kWh), thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like.

According to some embodiments, demand response layer 414 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer 418, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer 414 may also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer 414 uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models may represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).

Demand response layer 414 may further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user's application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.).

Integrated control layer 418 can be configured to use the data input or output of building subsystem integration layer 420 and/or demand response later 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integrated control layer 418 can integrate control activities of the subsystems 428 such that the subsystems 428 behave as a single integrated supersystem. In some embodiments, integrated control layer 418 includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer 418 can be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer 420.

Integrated control layer 418 is shown to be logically below demand response layer 414. Integrated control layer 418 can be configured to enhance the effectiveness of demand response layer 414 by enabling building subsystems 428 and their respective control loops to be controlled in coordination with demand response layer 414. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 418 can be configured to assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.

Integrated control layer 418 can be configured to provide feedback to demand response layer 414 so that demand response layer 414 checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints may also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 418 is also logically below fault detection and diagnostics layer 416 and automated measurement and validation layer 412. Integrated control layer 418 can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.

Automated measurement and validation (AM&V) layer 412 can be configured to verify that control strategies commanded by integrated control layer 418 or demand response layer 414 are working properly (e.g., using data aggregated by AM&V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or otherwise). The calculations made by AM&V layer 412 can be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example, AM&V layer 412 may compare a model-predicted output with an actual output from building subsystems 428 to determine an accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 can be configured to provide on-going fault detection for building subsystems 428, building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 may receive data inputs from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 may automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an alert message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to repair the fault or to work-around the fault.

FDD layer 416 can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 420. In other exemplary embodiments, FDD layer 416 is configured to provide “fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to some embodiments, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) may shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.

FDD layer 416 can be configured to store or access a variety of different system data stores (or data points for live data). FDD layer 416 may use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems 428 may generate temporal (i.e., time-series) data indicating the performance of BMS 400 and the various components thereof. The data generated by building subsystems 428 can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its setpoint. These processes can be examined by FDD layer 416 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe.

Referring now to FIG. 5, a block diagram of another building management system (BMS) 500 is shown, according to some embodiments. BMS 500 can be used to monitor and control the devices of HVAC system 100, waterside system 200, airside system 300, building subsystems 428, as well as other types of BMS devices (e.g., lighting equipment, security equipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automatic equipment discovery and equipment model distribution. Equipment discovery can occur on multiple levels of BMS 500 across multiple different communications busses (e.g., a system bus 554, zone buses 556-560 and 564, sensor/actuator bus 566, etc.) and across multiple different communications protocols. In some embodiments, equipment discovery is accomplished using active node tables, which provide status information for devices connected to each communications bus. For example, each communications bus can be monitored for new devices by monitoring the corresponding active node table for new nodes. When a new device is detected, BMS 500 can begin interacting with the new device (e.g., sending control signals, using data from the device) without user interaction.

Some devices in BMS 500 present themselves to the network using equipment models. An equipment model defines equipment object attributes, view definitions, schedules, trends, and the associated BACnet value objects (e.g., analog value, binary value, multistate value, etc.) that are used for integration with other systems. Some devices in BMS 500 store their own equipment models. Other devices in BMS 500 have equipment models stored externally (e.g., within other devices). For example, a zone coordinator 508 can store the equipment model for a bypass damper 528. In some embodiments, zone coordinator 508 automatically creates the equipment model for bypass damper 528 or other devices on zone bus 558. Other zone coordinators can also create equipment models for devices connected to their zone busses. The equipment model for a device can be created automatically based on the types of data points exposed by the device on the zone bus, device type, and/or other device attributes. Several examples of automatic equipment discovery and equipment model distribution are discussed in greater detail below.

Still referring to FIG. 5, BMS 500 is shown to include a system manager 502; several zone coordinators 506, 508, 510 and 518; and several zone controllers 524, 530, 532, 536, 548, and 550. System manager 502 can monitor data points in BMS 500 and report monitored variables to various monitoring and/or control applications. System manager 502 can communicate with client devices 504 (e.g., user devices, desktop computers, laptop computers, mobile devices, etc.) via a data communications link 574 (e.g., BACnet IP, Ethernet, wired or wireless communications, etc.). System manager 502 can provide a user interface to client devices 504 via data communications link 574. The user interface may allow users to monitor and/or control BMS 500 via client devices 504.

In some embodiments, system manager 502 is connected with zone coordinators 506-510 and 518 via a system bus 554. System manager 502 can be configured to communicate with zone coordinators 506-510 and 518 via system bus 554 using a master-slave token passing (MSTP) protocol or any other communications protocol. System bus 554 can also connect system manager 502 with other devices such as a constant volume (CV) rooftop unit (RTU) 512, an input/output module (IOM) 514, a thermostat controller 516 (e.g., a TEC5000 series thermostat controller), and a network automation engine (NAE) or third-party controller 520. RTU 512 can be configured to communicate directly with system manager 502 and can be connected directly to system bus 554. Other RTUs can communicate with system manager 502 via an intermediate device. For example, a wired input 562 can connect a third-party RTU 542 to thermostat controller 516, which connects to system bus 554.

System manager 502 can provide a user interface for any device containing an equipment model. Devices such as zone coordinators 506-510 and 518 and thermostat controller 516 can provide their equipment models to system manager 502 via system bus 554. In some embodiments, system manager 502 automatically creates equipment models for connected devices that do not contain an equipment model (e.g., IOM 514, third party controller 520, etc.). For example, system manager 502 can create an equipment model for any device that responds to a device tree request. The equipment models created by system manager 502 can be stored within system manager 502. System manager 502 can then provide a user interface for devices that do not contain their own equipment models using the equipment models created by system manager 502. In some embodiments, system manager 502 stores a view definition for each type of equipment connected via system bus 554 and uses the stored view definition to generate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or more of zone controllers 524, 530-532, 536, and 548-550 via zone buses 556, 558, 560, and 564. Zone coordinators 506-510 and 518 can communicate with zone controllers 524, 530-532, 536, and 548-550 via zone busses 556-560 and 564 using a MSTP protocol or any other communications protocol. Zone busses 556-560 and 564 can also connect zone coordinators 506-510 and 518 with other types of devices such as variable air volume (VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552, bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor and command various zoning systems. In some embodiments, each zone coordinator 506-510 and 518 monitors and commands a separate zoning system and is connected to the zoning system via a separate zone bus. For example, zone coordinator 506 can be connected to VAV RTU 522 and zone controller 524 via zone bus 556. Zone coordinator 508 can be connected to COBP RTU 526, bypass damper 528, COBP zone controller 530, and VAV zone controller 532 via zone bus 558. Zone coordinator 510 can be connected to PEAK controller 534 and VAV zone controller 536 via zone bus 560. Zone coordinator 518 can be connected to PEAK controller 544, bypass damper 546, COBP zone controller 548, and VAV zone controller 550 via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured to handle multiple different types of zoning systems (e.g., a VAV zoning system, a COBP zoning system, etc.). Each zoning system can include a RTU, one or more zone controllers, and/or a bypass damper. For example, zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs) connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 is connected directly to VAV RTU 522 via zone bus 556, whereas zone coordinator 510 is connected to a third-party VAV RTU 540 via a wired input 568 provided to PEAK controller 534. Zone coordinators 508 and 518 are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and 552, respectively. Zone coordinator 508 is connected directly to COBP RTU 526 via zone bus 558, whereas zone coordinator 518 is connected to a third-party COBP RTU 552 via a wired input 570 provided to PEAK controller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate with individual BMS devices (e.g., sensors, actuators, etc.) via sensor/actuator (SA) busses. For example, VAV zone controller 536 is shown connected to networked sensors 538 via SA bus 566. Zone controller 536 can communicate with networked sensors 538 using a MSTP protocol or any other communications protocol. Although only one SA bus 566 is shown in FIG. 5, it should be understood that each zone controller 524, 530-532, 536, and 548-550 can be connected to a different SA bus. Each SA bus can connect a zone controller with various sensors (e.g., temperature sensors, humidity sensors, pressure sensors, light sensors, occupancy sensors, etc.), actuators (e.g., damper actuators, valve actuators, etc.) and/or other types of controllable equipment (e.g., chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured to monitor and control a different building zone. Zone controllers 524, 530-532, 536, and 548-550 can use the inputs and outputs provided via their SA busses to monitor and control various building zones. For example, a zone controller 536 can use a temperature input received from networked sensors 538 via SA bus 566 (e.g., a measured temperature of a building zone) as feedback in a temperature control algorithm. Zone controllers 524, 530-532, 536, and 548-550 can use various types of control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control a variable state or condition (e.g., temperature, humidity, airflow, lighting, etc.) in or around building 10.

Model Predictive Maintenance System

Referring now to FIG. 6, a block diagram of a building system 600 is shown, according to an exemplary embodiment. System 600 may include many of the same components as BMS 400 and BMS 500 as described with reference to FIGS. 4-5. For example, system 600 is shown to include building 10, network 446, and client devices 448. Building 10 is shown to include connected equipment 610, which can include any type of equipment used to monitor and/or control building 10. Connected equipment 610 can include connected chillers 612, connected AHUs 614, connected boilers 616, connected batteries 618, or any other type of equipment in a building system (e.g., heaters, economizers, valves, actuators, dampers, cooling towers, fans, pumps, etc.) or building management system (e.g., lighting equipment, security equipment, refrigeration equipment, etc.). Connected equipment 610 can include any of the equipment of HVAC system 100, waterside system 200, airside system 300, BMS 400, and/or BMS 500, as described with reference to FIGS. 1-5.

Connected equipment 610 can be outfitted with sensors to monitor various conditions of the connected equipment 610 (e.g., power consumption, on/off states, operating efficiency, etc.). For example, chillers 612 can include sensors configured to monitor chiller variables such as chilled water temperature, condensing water temperature, and refrigerant properties (e.g., refrigerant pressure, refrigerant temperature, etc.) at various locations in the refrigeration circuit. An example of a chiller 700 which can be used as one of chillers 612 is shown in FIG. 7. Chiller 700 is shown to include a refrigeration circuit having a condenser 702, an expansion valve 704, an evaporator 706, a compressor 708, and a control panel 710. In some embodiments, chiller 700 includes sensors that measure a set of monitored variables at various locations along the refrigeration circuit. Similarly, AHUs 614 can be outfitted with sensors to monitor AHU variables such as supply air temperature and humidity, outside air temperature and humidity, return air temperature and humidity, chilled fluid temperature, heated fluid temperature, damper position, etc. In general, connected equipment 610 can monitor and report variables that characterize the performance of the connected equipment 610. Each monitored variable can be forwarded to building management system 606 as a data point including a point ID and a point value.

Monitored variables can include any measured or calculated values indicating the performance of connected equipment 610 and/or the components thereof. For example, monitored variables can include one or more measured or calculated temperatures (e.g., refrigerant temperatures, cold water supply temperatures, hot water supply temperatures, supply air temperatures, zone temperatures, etc.), pressures (e.g., evaporator pressure, condenser pressure, supply air pressure, etc.), flow rates (e.g., cold water flow rates, hot water flow rates, refrigerant flow rates, supply air flow rates, etc.), valve positions, resource consumptions (e.g., power consumption, water consumption, electricity consumption, etc.), control setpoints, model parameters (e.g., regression model coefficients), or any other time-series values that provide information about how the corresponding system, device, or process is performing. Monitored variables can be received from connected equipment 610 and/or from various components thereof. For example, monitored variables can be received from one or more controllers (e.g., BMS controllers, subsystem controllers, HVAC controllers, subplant controllers, AHU controllers, device controllers, etc.), BMS devices (e.g., chillers, cooling towers, pumps, heating elements, etc.), or collections of BMS devices.

Connected equipment 610 can also report equipment status information. Equipment status information can include, for example, the operational status of the equipment, an operating mode (e.g., low load, medium load, high load, etc.), an indication of whether the equipment is running under normal or abnormal conditions, the hours during which the equipment is running, a safety fault code, or any other information that indicates the current status of connected equipment 610. In some embodiments, each device of connected equipment 610 includes a control panel (e.g., control panel 710 shown in FIG. 7). Control panel 710 can be configured to collect monitored variables and equipment status information from connected equipment 610 and provide the collected data to BMS 606. For example, control panel 710 can compare the sensor data (or a value derived from the sensor data) to predetermined thresholds. If the sensor data or calculated value crosses a safety threshold, control panel 710 can shut down the device. Control panel 710 can generate a data point when a safety shut down occurs. The data point can include a safety fault code which indicates the reason or condition that triggered the shutdown.

Connected equipment 610 can provide monitored variables and equipment status information to BMS 606. BMS 606 can include a building controller (e.g., BMS controller 366), a system manager (e.g., system manager 502), a network automation engine (e.g., NAE 520), or any other system or device of building 10 configured to communicate with connected equipment 610. BMS 606 may include some or all of the components of BMS 400 or BMS 500, as described with reference to FIGS. 4-5. In some embodiments, the monitored variables and the equipment status information are provided to BMS 606 as data points. Each data point can include a point ID and a point value. The point ID can identify the type of data point or a variable measured by the data point (e.g., condenser pressure, refrigerant temperature, power consumption, etc.). Monitored variables can be identified by name or by an alphanumeric code (e.g., Chilled_Water_Temp, 7694, etc.). The point value can include an alphanumeric value indicating the current value of the data point.

BMS 606 can broadcast the monitored variables and the equipment status information to a model predictive maintenance system 602. In some embodiments, model predictive maintenance system 602 is a component of BMS 606. For example, model predictive maintenance system 602 can be implemented as part of a METASYS® brand building automation system, as sold by Johnson Controls Inc. In other embodiments, model predictive maintenance system 602 can be a component of a remote computing system or cloud-based computing system configured to receive and process data from one or more building management systems via network 446. For example, model predictive maintenance system 602 can be implemented as part of a PANOPTIX® brand building efficiency platform, as sold by Johnson Controls Inc. In other embodiments, model predictive maintenance system 602 can be a component of a subsystem level controller (e.g., a HVAC controller), a subplant controller, a device controller (e.g., AHU controller 330, a chiller controller, etc.), a field controller, a computer workstation, a client device, or any other system or device that receives and processes monitored variables from connected equipment 610.

Model predictive maintenance (MPM) system 602 may use the monitored variables and/or the equipment status information to identify a current operating state of connected equipment 610. The current operating state can be examined by MPM system 602 to expose when connected equipment 610 begins to degrade in performance and/or to predict when faults will occur. In some embodiments, MPM system 602 uses the information collected from connected equipment 610 to estimate the reliability of connected equipment 610. For example, MPM system 602 can estimate a likelihood of various types of failures that could potentially occur based on the current operating conditions of connected equipment 610 and an amount of time that has elapsed since connected equipment 610 has been installed and/or since maintenance was last performed. In some embodiments, MPM system 602 estimates an amount of time until each failure is predicted to occur and identifies a financial cost associated with each failure (e.g., maintenance cost, increased operating cost, replacement cost, etc.). MPM system 602 can use the reliability information and the likelihood of potential failures to predict when maintenance will be needed and to estimate the cost of performing such maintenance over a predetermined time period.

MPM system 602 can be configured to determine an optimal maintenance strategy for connected equipment 610. In some embodiments, the optimal maintenance strategy is a set of decisions which optimizes the total cost associated with purchasing, maintaining, and operating connected equipment 610 over the duration of an optimization period (e.g., 30 weeks, 52 weeks, 10 years, 30 years, etc.). The decisions can include, for example, equipment purchase decisions, equipment maintenance decisions, and equipment operating decisions. MPM system 602 can use a model predictive control technique to formulate an objective function which expresses the total cost as a function of these decisions, which can be included as decision variables in the objective function. MPM system 602 can optimize (i.e., minimize) the objective function using any of a variety of optimization techniques to identify the optimal values for each of the decision variables.

One example of an objective function which can be optimized by MPM system 602 is shown in the following equation:

$J = {{\sum\limits_{i = 1}^{h}\;{C_{{op},i}P_{{op},i}\Delta\; t}} + {\sum\limits_{i = 1}^{h}\;{C_{{main},i}B_{{main},i}}} + {\sum\limits_{i = 1}^{h}\;{C_{{cap},i}P_{{cap},i}}}}$ where C_(op,i) is the cost per unit of energy (e.g., $/kWh) consumed by connected equipment 610 at time step i of the optimization period, P_(op,i) is the power consumption (e.g., kW) of connected equipment 610 at time step i, Δt is the duration of each time step i, C_(main,i) is the cost of maintenance performed on connected equipment 610 at time step i, B_(main,i) is a binary variable that indicates whether the maintenance is performed, C_(cap,i) is the capital cost of purchasing a new device of connected equipment 610 at time step i, B_(cap,i) is a binary variable that indicates whether the new device is purchased, and h is the duration of the horizon or optimization period over which the optimization is performed.

The first term in the objective function J represents the operating cost of connected equipment 610 over the duration of the optimization period. In some embodiments, the cost per unit of energy C_(op,i) is received from a utility 608 as energy pricing data. The cost C_(op,i) may be a time-varying cost that depends on the time of day, the day of the week (e.g., weekday vs. weekend), the current season (e.g., summer vs. winter), or other time-based factors. For example, the cost C_(op,i) may be higher during peak energy consumption periods and lower during off-peak or partial-peak energy consumption periods.

In some embodiments, the power consumption P_(op,i) is based on the heating or cooling load of building 10. The heating or cooling load can be predicted by MPM system 602 as a function of building occupancy, the time of day, the day of the week, the current season, or other factors that can affect the heating or cooling load. In some embodiments, MPM system 602 uses weather forecasts from a weather service 604 to predict the heating or cooling load. The power consumption P_(op,i) may also depend on the efficiency η_(i) of connected equipment 610. For example, connected equipment 610 that operate at a high efficiency may consume less power P_(op,i) to satisfy the same heating or cooling load relative to connected equipment 610 that operate at a low efficiency. In general, the power consumption P_(op,i) of a particular device of connected equipment 610 can be modeled using the following equations:

$P_{{op},i} = \frac{P_{{ideal},i}}{\eta_{i}}$ P_(ideal, i) = f(Load_(i)) where Load_(i) is the heating or cooling load on the device at time step i (e.g., tons cooling, kW heating, etc.), P_(ideal,i) is the value of the equipment performance curve (e.g., tons cooling, kW heating, etc.) for the device at the corresponding load point Load_(i), and η_(i) is the operating efficiency of the device at time step i (e.g., 0≤η_(i)≤1). The function ƒ(Load_(i)) may be defined by the equipment performance curve for the device or set of devices represented by the performance curve.

In some embodiments, the equipment performance curve is based on manufacturer specifications for the device under ideal operating conditions. For example, the equipment performance curve may define the relationship between power consumption and heating/cooling load for each device of connected equipment 610. However, the actual performance of the device may vary as a function of the actual operating conditions. MPM system 602 can analyze the equipment performance information provided by connected equipment 610 to determine the operating efficiency η_(i) for each device of connected equipment 610. In some embodiments, MPM system 602 uses the equipment performance information from connected equipment 610 to determine the actual operating efficiency η_(i) for each device of connected equipment 610. MPM system 602 can use the operating efficiency η_(i) as an input to the objective function J and/or to calculate the corresponding value of P_(op,i).

Advantageously, MPM system 602 can model the efficiency η_(i) of connected equipment 610 at each time step i as a function of the maintenance decisions B_(main,i) and the equipment purchase decisions B_(cap,i). For example, the efficiency η_(i) for a particular device may start at an initial value η₀ when the device is purchased and may degrade over time such that the efficiency η_(i) decreases with each successive time step i. Performing maintenance on a device may reset the efficiency η_(i) to a higher value immediately after the maintenance is performed. Similarly, purchasing a new device to replace an existing device may reset the efficiency η_(i) to a higher value immediately after the new device is purchased. After being reset, the efficiency η_(i) may continue to degrade over time until the next time at which maintenance is performed or a new device is purchased.

Performing maintenance or purchasing a new device may result in a relatively lower power consumption P_(op,i) during operation and therefore a lower operating cost at each time step i after the maintenance is performed or the new device is purchased. In other words, performing maintenance or purchasing a new device may decrease the operating cost represented by the first term of the objective function J. However, performing maintenance may increase the second term of the objective function J and purchasing a new device may increase the third term of the objective function J. The objective function J captures each of these costs and can be optimized by MPM system 602 to determine the optimal set of maintenance and equipment purchase decisions (i.e., optimal values for the binary decision variables B_(main,i) and B_(cap,i)) over the duration of the optimization period.

In some embodiments, MPM system 602 uses the equipment performance information from connected equipment 610 to estimate the reliability of connected equipment 610. The reliability may be a statistical measure of the likelihood that connected equipment 610 will continue operating without fault under its current operating conditions. Operating under more strenuous conditions (e.g., high load, high temperatures, etc.) may result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) may result in a higher reliability. In some embodiments, the reliability is based on an amount of time that has elapsed since connected equipment 610 last received maintenance.

MPM system 602 may receive operating data from a plurality of devices of connected equipment 610 distributed across multiple buildings and can use the set of operating data (e.g., operating conditions, fault indications, failure times, etc.) to develop a reliability model for each type of equipment. The reliability models can be used by MPM system 602 to estimate the reliability of any given device of connected equipment 610 as a function of its current operating conditions and/or other extraneous factors (e.g., time since maintenance was last performed, geographic location, water quality, etc.). In some embodiments, MPM system 602 uses the estimated reliability of each device of connected equipment 610 to determine the probability that the device will require maintenance and/or replacement at each time step of the optimization period. MPM system 602 can use these probabilities to determine the optimal set of maintenance and equipment purchase decisions (i.e., optimal values for the binary decision variables B_(main,i) and B_(cap,i)) over the duration of the optimization period.

In some embodiments, MPM system 602 generates and provides equipment purchase and maintenance recommendations. The equipment purchase and maintenance recommendations may be based on the optimal values for the binary decision variables B_(main,i) and B_(cap,i) determined by optimizing the objective function J. For example, a value of B_(main,25)=1 for a particular device of connected equipment 610 may indicate that maintenance should be performed on that device at the 25^(th) time step of the optimization period, whereas a value of B_(main,25)=0 may indicate that the maintenance should not be performed at that time step. Similarly, a value of B_(cap,25)=1 may indicate that a new device of connected equipment 610 should be purchased at the 25^(th) time step of the optimization period, whereas a value of B_(cap,25)=0 may indicate that the new device should not be purchased at that time step.

Advantageously, the equipment purchase and maintenance recommendations generated by MPM system 602 are predictive recommendations based on the actual operating conditions and actual performance of connected equipment 610. The optimization performed by MPM system 602 weighs the cost of performing maintenance and the cost of purchasing new equipment against the decrease in operating cost resulting from such maintenance or purchase decisions in order to determine the optimal maintenance strategy that minimizes the total combined cost. In this way, the equipment purchase and maintenance recommendations generated by MPM system 602 may be specific to each group of connected equipment 610 in order to achieve the optimal cost J for that specific group of connected equipment 610. The equipment-specific recommendations may result in a lower overall cost J relative to generic preventative maintenance recommendations provided by an equipment manufacturer (e.g., service equipment every year) which may be sub-optimal for some groups of connected equipment 610 and/or some operating conditions.

In some embodiments, the equipment purchase and maintenance recommendations are provided to building 10 (e.g., to BMS 606) and/or to client devices 448. An operator or building owner can use the equipment purchase and maintenance recommendations to assess the costs and benefits of performing maintenance and purchasing new devices. In some embodiments, the equipment purchase and maintenance recommendations are provided to service technicians 620. Service technicians 620 can use the equipment purchase and maintenance recommendations to determine when customers should be contacted to perform service or replace equipment.

In some embodiments, MPM system 602 includes a data analytics and visualization platform. MPM system 602 may provide a web interface which can be accessed by service technicians 620, client devices 448, and other systems or devices. The web interface can be used to access the equipment performance information, view the results of the optimization, identify which equipment is in need of maintenance, and otherwise interact with MPM system 602. Service technicians 620 can access the web interface to view a list of equipment for which maintenance is recommended by MPM system 602. Service technicians 620 can use the equipment purchase and maintenance recommendations to proactively repair or replace connected equipment 610 in order to achieve the optimal cost predicted by the objective function J. These and other features of MPM system 602 are described in greater detail below.

Referring now to FIG. 8, a block diagram illustrating MPM system 602 in greater detail is shown, according to an exemplary embodiment. MPM system 602 is shown providing optimization results to a building management system (BMS) 606. BMS 606 can include some or all of the features of BMS 400 and/or BMS 500, as described with reference to FIGS. 4-5. The optimization results provided to BMS 606 may include the optimal values of the decision variables in the objective function J for each time step i in the optimization period. In some embodiments, the optimization results include equipment purchase and maintenance recommendations for each device of connected equipment 610.

BMS 606 may be configured to monitor the operation and performance of connected equipment 610. BMS 606 may receive monitored variables from connected equipment 610. Monitored variables can include any measured or calculated values indicating the performance of connected equipment 610 and/or the components thereof. For example, monitored variables can include one or more measured or calculated temperatures, pressures, flow rates, valve positions, resource consumptions (e.g., power consumption, water consumption, electricity consumption, etc.), control setpoints, model parameters (e.g., equipment model coefficients), or any other variables that provide information about how the corresponding system, device, or process is performing.

In some embodiments, the monitored variables indicate the operating efficiency η_(i) of each device of connected equipment 610 or can be used to calculate the operating efficiency η_(i). For example, the temperature and flow rate of chilled water output by a chiller can be used to calculate the cooling load (e.g., tons cooling) served by the chiller. The cooling load can be used in combination with the power consumption of the chiller to calculate the operating efficiency η_(i) (e.g., tons cooling per kW of electricity consumed). BMS 606 may report the monitored variables to MPM system 602 for use in calculating the operating efficiency η_(i) of each device of connected equipment 610.

In some embodiments, BMS 606 monitors the run hours of connected equipment 610. The run hours may indicate the number of hours within a given time period during which each device of connected equipment 610 is active. For example, the run hours for a chiller may indicate that the chiller is active for approximately eight hours per day. The run hours can be used in combination with the average power consumption of the chiller when active to estimate the total power consumption P_(op,i) of connected equipment 610 at each time step i.

In some embodiments, BMS 606 monitors the equipment failures and fault indications reported by connected equipment 610. BMS 606 can record the times at which each failure or fault occurs and the operating conditions of connected equipment 610 under which the fault or failure occurred. The operating data collected from connected equipment 610 can be used by BMS 606 and/or MPM system 602 to develop a reliability model for each device of connected equipment 610. BMS 606 may provide the monitored variables, the equipment run hours, the operating conditions, and the equipment failures and fault indications to MPM system 602 as equipment performance information.

BMS 606 may be configured to monitor conditions within a controlled building or building zone. For example, BMS 606 may receive input from various sensors (e.g., temperature sensors, humidity sensors, airflow sensors, voltage sensors, etc.) distributed throughout the building and may report building conditions to MPM system 602. Building conditions may include, for example, a temperature of the building or a zone of the building, a power consumption (e.g., electric load) of the building, a state of one or more actuators configured to affect a controlled state within the building, or other types of information relating to the controlled building. BMS 606 may operate connected equipment 610 to affect the monitored conditions within the building and to serve the thermal energy loads of the building.

BMS 606 may provide control signals to connected equipment 610 specifying on/off states, charge/discharge rates, and/or setpoints for connected equipment 610. BMS 606 may control the equipment (e.g., via actuators, power relays, etc.) in accordance with the control signals to achieve setpoints for various building zones and/or devices of connected equipment 610. In various embodiments, BMS 606 may be combined with MPM system 602 or may be part of a separate building management system. According to an exemplary embodiment, BMS 606 is a METASYS® brand building management system, as sold by Johnson Controls, Inc.

MPM system 602 may monitor the performance of connected equipment 610 using information received from BMS 606. MPM system 602 may be configured to predict the thermal energy loads (e.g., heating loads, cooling loads, etc.) of the building for plurality of time steps in the optimization period (e.g., using weather forecasts from a weather service 604). MPM system 602 may also predict the cost of electricity or other resources (e.g., water, natural gas, etc.) using pricing data received from utilities 608. MPM system 602 may generate optimization results that optimize the economic value of operating, maintaining, and purchasing connected equipment 610 over the duration of the optimization period subject to constraints on the optimization process (e.g., load constraints, decision variable constraints, etc.). The optimization process performed by MPM system 602 is described in greater detail below.

According to an exemplary embodiment, MPM system 602 can be integrated within a single computer (e.g., one server, one housing, etc.). In various other exemplary embodiments, MPM system 602 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). In another exemplary embodiment, MPM system 602 may integrated with a smart building manager that manages multiple building systems and/or combined with BMS 606.

MPM system 602 is shown to include a communications interface 804 and a processing circuit 806. Communications interface 804 may include wired or wireless interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with various systems, devices, or networks. For example, communications interface 804 may include an Ethernet card and port for sending and receiving data via an Ethernet-based communications network and/or a WiFi transceiver for communicating via a wireless communications network. Communications interface 804 may be configured to communicate via local area networks or wide area networks (e.g., the Internet, a building WAN, etc.) and may use a variety of communications protocols (e.g., BACnet, IP, LON, etc.).

Communications interface 804 may be a network interface configured to facilitate electronic data communications between MPM system 602 and various external systems or devices (e.g., BMS 606, connected equipment 610, utilities 510, etc.). For example, MPM system 602 may receive information from BMS 606 indicating one or more measured states of the controlled building (e.g., temperature, humidity, electric loads, etc.) and equipment performance information for connected equipment 610 (e.g., run hours, power consumption, operating efficiency, etc.). Communications interface 804 may receive inputs from BMS 606 and/or connected equipment 610 and may provide optimization results to BMS 606 and/or other external systems or devices. The optimization results may cause BMS 606 to activate, deactivate, or adjust a setpoint for connected equipment 610 in order to achieve the optimal values of the decision variables specified in the optimization results.

Still referring to FIG. 8, processing circuit 806 is shown to include a processor 808 and memory 810. Processor 808 may be a general purpose or specific purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable processing components. Processor 808 may be configured to execute computer code or instructions stored in memory 810 or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.).

Memory 810 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. Memory 810 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. Memory 810 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. Memory 810 may be communicably connected to processor 808 via processing circuit 806 and may include computer code for executing (e.g., by processor 808) one or more processes described herein.

MPM system 602 is shown to include an equipment performance monitor 824. Equipment performance monitor 824 can receive equipment performance information from BMS 606 and/or connected equipment 610. The equipment performance information can include samples of monitored variables (e.g., measured temperature, measured pressure, measured flow rate, power consumption, etc.), current operating conditions (e.g., heating or cooling load, current operating state, etc.), fault indications, or other types of information that characterize the performance of connected equipment 610. In some embodiments, equipment performance monitor 824 uses the equipment performance information to calculate the current efficiency η_(i) and reliability of each device of connected equipment 610. Equipment performance monitor 824 can provide the efficiency η_(i) and reliability values to model predictive optimizer 830 for use in optimizing the objective function J.

Still referring to FIG. 8, MPM system 602 is shown to include a load/rate predictor 822. Load/rate predictor 822 may be configured to predict the energy loads (Load_(i)) (e.g., heating load, cooling load, electric load, etc.) of the building or campus for each time step i of the optimization period. Load/rate predictor 822 is shown receiving weather forecasts from a weather service 604. In some embodiments, load/rate predictor 822 predicts the energy loads Load_(i) as a function of the weather forecasts. In some embodiments, load/rate predictor 822 uses feedback from BMS 606 to predict loads Load_(i). Feedback from BMS 606 may include various types of sensory inputs (e.g., temperature, flow, humidity, enthalpy, etc.) or other data relating to the controlled building (e.g., inputs from a HVAC system, a lighting control system, a security system, a water system, etc.).

In some embodiments, load/rate predictor 822 receives a measured electric load and/or previous measured load data from BMS 606 (e.g., via equipment performance monitor 824). Load/rate predictor 822 may predict loads Load_(i) as a function of a given weather forecast ({circumflex over (ϕ)}_(w)), a day type (day), the time of day (t), and previous measured load data (Y_(i-1)). Such a relationship is expressed in the following equation: Load_(i)=ƒ({circumflex over (ϕ)}_(w), day, t|Y _(i-1))

In some embodiments, load/rate predictor 822 uses a deterministic plus stochastic model trained from historical load data to predict loads Load_(i). Load/rate predictor 822 may use any of a variety of prediction methods to predict loads Load_(i) (e.g., linear regression for the deterministic portion and an AR model for the stochastic portion). Load/rate predictor 822 may predict one or more different types of loads for the building or campus. For example, load/rate predictor 822 may predict a hot water load Load_(Hot,i), a cold water load Load_(Cold,i), and an electric load Load_(Elec,i) for each time step i within the optimization period. The predicted load values Load_(i) can include some or all of these types of loads. In some embodiments, load/rate predictor 822 makes load/rate predictions using the techniques described in U.S. patent application Ser. No. 14/717,593.

Load/rate predictor 822 is shown receiving utility rates from utilities 608. Utility rates may indicate a cost or price per unit of a resource (e.g., electricity, natural gas, water, etc.) provided by utilities 608 at each time step i in the optimization period. In some embodiments, the utility rates are time-variable rates. For example, the price of electricity may be higher at certain times of day or days of the week (e.g., during high demand periods) and lower at other times of day or days of the week (e.g., during low demand periods). The utility rates may define various time periods and a cost per unit of a resource during each time period. Utility rates may be actual rates received from utilities 608 or predicted utility rates estimated by load/rate predictor 822.

In some embodiments, the utility rates include demand charges for one or more resources provided by utilities 608. A demand charge may define a separate cost imposed by utilities 608 based on the maximum usage of a particular resource (e.g., maximum energy consumption) during a demand charge period. The utility rates may define various demand charge periods and one or more demand charges associated with each demand charge period. In some instances, demand charge periods may overlap partially or completely with each other and/or with the prediction window. Model predictive optimizer 830 may be configured to account for demand charges in the high level optimization process performed by high level optimizer 832. Utilities 608 may be defined by time-variable (e.g., hourly) prices, a maximum service level (e.g., a maximum rate of consumption allowed by the physical infrastructure or by contract) and, in the case of electricity, a demand charge or a charge for the peak rate of consumption within a certain period. Load/rate predictor 822 may store the predicted loads Load_(i) and the utility rates in memory 810 and/or provide the predicted loads Load_(i) and the utility rates to model predictive optimizer 830.

Still referring to FIG. 8, MPM system 602 is shown to include a model predictive optimizer 830. Model predictive optimizer 830 can be configured to perform a multi-level optimization process to optimize the total cost associated with purchasing, maintaining, and operating connected equipment 610. In some embodiments, model predictive optimizer 830 includes a high level optimizer 832 and a low level optimizer 834. High level optimizer 832 may optimize the objective function J for an entire set of connected equipment 610 (e.g., all of the devices within a building) or for a subset of connected equipment 610 (e.g., a single device, all of the devices of a subplant or building subsystem, etc.) to determine the optimal values for each of the decision variables (e.g., P_(op,i), B_(main,i), and B_(cap,i)) in the objective function J. The optimization performed by high level optimizer 832 is described in greater detail with reference to FIG. 9.

In some embodiments, low level optimizer 834 receives the optimization results from high level optimizer 832. The optimization results may include optimal power consumption values P_(op,i) and/or load values Load_(i) for each device or set of devices of connected equipment at each time step i in the optimization period. Low level optimizer 834 may determine how to best run each device or set of devices at the load values determined by high level optimizer 832. For example, low level optimizer 834 may determine on/off states and/or operating setpoints for various devices of connected equipment 610 in order to optimize (e.g., minimize) the power consumption of connected equipment 610 meeting the corresponding load value Load_(i).

Low level optimizer 834 may be configured to generate equipment performance curves for each device or set of devices of connected equipment 610. Each performance curve may indicate an amount of resource consumption (e.g., electricity use measured in kW, water use measured in L/s, etc.) by a particular device or set of devices of connected equipment 610 as a function of the load on the device or set of devices. In some embodiments, low level optimizer 834 generates the performance curves by performing a low level optimization process at various combinations of load points (e.g., various values of Load_(i)) and weather conditions to generate multiple data points. The low level optimization may be used to determine the minimum amount of resource consumption required to satisfy the corresponding heating or cooling load. An example of a low level optimization process which can be performed by low level optimizer 834 is described in detail in U.S. patent application Ser. No. 14/634,615 titled “Low Level Central Plant Optimization” and filed Feb. 27, 2015, the entire disclosure of which is incorporated by reference herein. Low level optimizer 834 may fit a curve to the data points to generate the performance curves.

In some embodiments, low level optimizer 834 generates equipment performance curves for a set of connected equipment 610 (e.g., a chiller subplant, a heater subplant, etc.) by combining efficiency curves for individual devices of connected equipment 610. A device efficiency curve may indicate the amount of resource consumption by the device as a function of load. The device efficiency curves may be provided by a device manufacturer or generated using experimental data. In some embodiments, the device efficiency curves are based on an initial efficiency curve provided by a device manufacturer and updated using experimental data. The device efficiency curves may be stored in equipment models 818. For some devices, the device efficiency curves may indicate that resource consumption is a U-shaped function of load. Accordingly, when multiple device efficiency curves are combined into a performance curve for multiple devices, the resultant performance curve may be a wavy curve. The waves are caused by a single device loading up before it is more efficient to turn on another device to satisfy the subplant load. Low level optimizer 834 may provide the equipment performance curves to high level optimizer 832 for use in the high level optimization process.

Still referring to FIG. 8, MPM system 602 is shown to include an equipment controller 828. Equipment controller 828 can be configured to control connected equipment 610 to affect a variable state or condition in building 10 (e.g., temperature, humidity, etc.). In some embodiments, equipment controller 828 controls connected equipment 610 based on the results of the optimization performed by model predictive optimizer 830. In some embodiments, equipment controller 828 generates control signals which can be provided to connected equipment 610 via communications interface 804 and/or BMS 606. The control signals may be based on the optimal values of the decision variables in the objective function J. For example, equipment controller 828 may generate control signals which cause connected equipment 610 to achieve the optimal power consumption values P_(op,i) for each time step i in the optimization period.

Data and processing results from model predictive optimizer 830, equipment controller 828, or other modules of MPM system 602 may be accessed by (or pushed to) monitoring and reporting applications 826. Monitoring and reporting applications 826 may be configured to generate real time “system health” dashboards that can be viewed and navigated by a user (e.g., a system engineer). For example, monitoring and reporting applications 826 may include a web-based monitoring application with several graphical user interface (GUI) elements (e.g., widgets, dashboard controls, windows, etc.) for displaying key performance indicators (KPI) or other information to users of a GUI. In addition, the GUI elements may summarize relative energy use and intensity across building management systems in different buildings (real or modeled), different campuses, or the like. Other GUI elements or reports may be generated and shown based on available data that allow users to assess performance across one or more energy storage systems from one screen. The user interface or report (or underlying data engine) may be configured to aggregate and categorize operating conditions by building, building type, equipment type, and the like. The GUI elements may include charts or histograms that allow the user to visually analyze the operating parameters and power consumption for the devices of the building system.

Still referring to FIG. 8, MPM system 602 may include one or more GUI servers, web services 812, or GUI engines 814 to support monitoring and reporting applications 826. In various embodiments, applications 826, web services 812, and GUI engine 814 may be provided as separate components outside of MPM system 602 (e.g., as part of a smart building manager). MPM system 602 may be configured to maintain detailed historical databases (e.g., relational databases, XML databases, etc.) of relevant data and includes computer code modules that continuously, frequently, or infrequently query, aggregate, transform, search, or otherwise process the data maintained in the detailed databases. MPM system 602 may be configured to provide the results of any such processing to other databases, tables, XML files, or other data structures for further querying, calculation, or access by, for example, external monitoring and reporting applications.

MPM system 602 is shown to include configuration tools 816. Configuration tools 816 can allow a user to define (e.g., via graphical user interfaces, via prompt-driven “wizards,” etc.) how MPM system 602 should react to changing conditions in BMS 606 and/or connected equipment 610. In an exemplary embodiment, configuration tools 816 allow a user to build and store condition-response scenarios that can cross multiple devices of connected equipment 610, multiple building systems, and multiple enterprise control applications (e.g., work order management system applications, entity resource planning applications, etc.). For example, configuration tools 816 can provide the user with the ability to combine data (e.g., from subsystems, from event histories) using a variety of conditional logic. In varying exemplary embodiments, the conditional logic can range from simple logical operators between conditions (e.g., AND, OR, XOR, etc.) to pseudo-code constructs or complex programming language functions (allowing for more complex interactions, conditional statements, loops, etc.). Configuration tools 816 can present user interfaces for building such conditional logic. The user interfaces may allow users to define policies and responses graphically. In some embodiments, the user interfaces may allow a user to select a pre-stored or pre-constructed policy and adapt it or enable it for use with their system.

High Level Optimizer

Referring now to FIG. 9, a block diagram illustrating high level optimizer 832 in greater detail is shown, according to an exemplary embodiment. High level optimizer 832 can be configured to determine an optimal maintenance strategy for connected equipment 610. In some embodiments, the optimal maintenance strategy is a set of decisions which optimizes the total cost associated with purchasing, maintaining, and operating connected equipment 610 over the duration of an optimization period (e.g., 30 weeks, 52 weeks, 10 years, 30 years, etc.). The decisions can include, for example, equipment purchase decisions, equipment maintenance decisions, and equipment operating decisions.

High level optimizer 832 is shown to include an operational cost predictor 910, a maintenance cost predictor 920, a capital cost predictor 930, an objective function generator 935, and an objective function optimizer 940. Cost predictors 910, 920, and 930 can use a model predictive control technique to formulate an objective function which expresses the total cost as a function of several decision variables (e.g., maintenance decisions, equipment purchase decisions, etc.) and input parameters (e.g., energy cost, device efficiency, device reliability). Operational cost predictor 910 can be configured to formulate an operational cost term in the objective function. Similarly, maintenance cost predictor 920 can be configured to formulate a maintenance cost term in the objective function and capital cost predictor 930 can be configured to formulate a capital cost term in the objective function. Objective function optimizer 940 can optimize (i.e., minimize) the objective function using any of a variety of optimization techniques to identify the optimal values for each of the decision variables.

One example of an objective function which can be generated by high level optimizer 832 is shown in the following equation:

$J = {{\sum\limits_{i = 1}^{h}\;{C_{{op},i}P_{{op},i}\Delta\; t}} + {\sum\limits_{i = 1}^{h}\;{C_{{main},i}B_{{main},i}}} + {\sum\limits_{i = 1}^{h}\;{C_{{cap},i}P_{{cap},i}}}}$ where C_(op,i) is the cost per unit of energy (e.g., $/kWh) consumed by connected equipment 610 at time step i of the optimization period, P_(op,i) is the power consumption (e.g., kW) of connected equipment 610 at time step i, Δt is the duration of each time step i, C_(main,i) is the cost of maintenance performed on connected equipment 610 at time step i, B_(main,i) is a binary variable that indicates whether the maintenance is performed, C_(cap,i) is the capital cost of purchasing a new device of connected equipment 610 at time step i, B_(cap,i) is a binary variable that indicates whether the new device is purchased, and h is the duration of the horizon or optimization period over which the optimization is performed. Operational Cost Predictor

Operational cost predictor 910 can be configured to formulate the first term in the objective function J. The first term in the objective function J represents the operating cost of connected equipment 610 over the duration of the optimization period and is shown to include three variables or parameters (i.e., C_(op,i), P_(op,i), and Δt). In some embodiments, the cost per unit of energy C_(op,i) is determined by energy costs module 915. Energy costs module 915 can receive a set of energy prices from utility 608 as energy pricing data. In some embodiments, the energy prices are time-varying cost that depend on the time of day, the day of the week (e.g., weekday vs. weekend), the current season (e.g., summer vs. winter), or other time-based factors. For example, the cost of electricity may be higher during peak energy consumption periods and lower during off-peak or partial-peak energy consumption periods.

Energy costs module 915 can use the energy costs to define the value of C_(op,i) for each time step i of the optimization period. In some embodiments, energy costs module 915 stores the energy costs as an array C_(op) including a cost element for each of the h time steps in the optimization period. For example, energy costs module 915 can generate the following array: C _(op)=[C _(op,1) C _(op,2) . . . C _(op,h)] where the array C_(op) has a size of 1×h and each element of the array C_(op) includes an energy cost value C_(op,i) for a particular time step i=1 . . . h of the optimization period.

Still referring to FIG. 9, operational cost predictor 910 is shown to include an ideal performance calculator 912. Ideal performance calculator 912 may receive load predictions Load_(i) from load/rate predictor 822 and may receive performance curves from low level optimizer 834. As discussed above, the performance curves may define the ideal power consumption P_(ideal) of a device or set of devices of connected equipment 610 as a function of the heating or cooling load on the device or set of devices. For example, the performance curve one or more devices of connected equipment 610 can be defined by the following equation: P _(ideal,i)=ƒ(Load_(i)) where P_(ideal,i) is the ideal power consumption (e.g., kW) of connected equipment 610 at time step i and Load_(i) is the load (e.g., tons cooling, kW heating, etc.) on connected equipment 610 at time step i. The ideal power consumption P_(ideal,i) may represent the power consumption of the one or more devices of connected equipment 610 assuming they operate at perfect efficiency.

Ideal performance calculator 912 can use the performance curve for a device or set of devices of connected equipment 610 to identify the value of P_(ideal,i) that corresponds to the load point Load_(i) for the device or set of devices at each time step of the optimization period. In some embodiments, ideal performance calculator 912 stores the ideal load values as an array P_(ideal) including an element for each of the h time steps in the optimization period. For example, ideal performance calculator 912 can generate the following array: P _(ideal)=[P _(ideal,1) P _(ideal,2) . . . P _(ideal,h)]^(T) where the array P_(ideal) has a size of h×1 and each element of the array P_(ideal) includes an ideal power consumption value P_(ideal,i) for a particular time step i=1 . . . h of the optimization period.

Still referring to FIG. 9, operational cost predictor 910 is shown to include an efficiency updater 911 and an efficiency degrader 913. Efficiency updater 911 can be configured to determine the efficiency η of connected equipment 610 under actual operating conditions. In some embodiments, the efficiency η_(i) represents the ratio of the ideal power consumption P_(ideal) of connected equipment to the actual power consumption P_(actual) of connected equipment 610, as shown in the following equation:

$\eta = \frac{P_{ideal}}{P_{actual}}$ where P_(ideal) is the ideal power consumption of connected equipment 610 as defined by the performance curve for connected equipment 610 and P_(actual) is the actual power consumption of connected equipment 610. In some embodiments, efficiency updater 911 uses the equipment performance information collected from connected equipment 610 to identify the actual power consumption value P_(actual). Efficiency updater 911 can use the actual power consumption P_(actual) in combination with the ideal power consumption P_(ideal) to calculate the efficiency η.

Efficiency updater 911 can be configured to periodically update the efficiency η to reflect the current operating efficiency of connected equipment 610. For example, efficiency updater 911 can calculate the efficiency η of connected equipment 610 once per day, once per week, once per year, or at any other interval as may be suitable to capture changes in the efficiency η over time. Each value of the efficiency η1 may be based on corresponding values of P_(ideal) and P_(actual) at the time the efficiency η is calculated. In some embodiments, efficiency updater 911 updates the efficiency η each time the high level optimization process is performed (i.e., each time the objective function J is optimized). The efficiency value calculated by efficiency updater 911 may be stored in memory 810 as an initial efficiency value η₀, where the subscript 0 denotes the value of the efficiency η at or before the beginning of the optimization period (e.g., at time step 0).

In some embodiments, efficiency updater 911 updates the efficiency η_(i) for one or more time steps during the optimization period to account for increases in the efficiency ηof connected equipment 610 that will result from performing maintenance on connected equipment 610 or purchasing new equipment to replace or supplement one or more devices of connected equipment 610. The time steps i at which the efficiency η_(i) is updated may correspond to the predicted time steps at which the maintenance will be performed or the equipment will replaced. The predicted time steps at which maintenance will be performed on connected equipment 610 may be defined by the values of the binary decision variables B_(main,i) in the objective function j. Similarly, the predicted time steps at which the equipment will be replaced may be defined by the values of the binary decision variables B_(cap,i) in the objective function J.

Efficiency updater 911 can be configured to reset the efficiency η_(i) for a given time step i if the binary decision variables B_(main,i) and B_(cap,i) indicate that maintenance will be performed at that time step and/or new equipment will be purchased at that time step (i.e., B_(main,i)=1 and/or B_(cap,i)=1). For example, if B_(main,i)=1, efficiency updater 911 can be configured to reset the value of η_(i) to η_(main), where η_(main) is the efficiency value that is expected to result from the maintenance performed at time step i. Similarly, if B_(cap,i)=1, efficiency updater 911 can be configured to reset the value of η to η_(cap), where η_(cap) is the efficiency value that is expected to result from purchasing a new device to supplement or replace one or more devices of connected equipment 610 performed at time step i. Efficiency updater 911 can dynamically reset the efficiency η_(i) for one or more time steps while the optimization is being performed (e.g., with each iteration of the optimization) based on the values of binary decision variables B_(main,i) and B_(cap,i).

Efficiency degrader 913 can be configured to predict the efficiency η_(i) of connected equipment 610 at each time step i of the optimization period. The initial efficiency η₀ at the beginning of the optimization period may degrade over time as connected equipment 610 degrade in performance. For example, the efficiency of a chiller may degrade over time as a result of the chilled water tubes becoming dirty and reducing the heat transfer coefficient of the chiller. Similarly, the efficiency of a battery may decrease over time as a result of degradation in the physical or chemical components of the battery. Efficiency degrader 913 can be configured to account for such degradation by incrementally reducing the efficiency η_(i) over the duration of the optimization period.

In some embodiments, the initial efficiency value η₀ is updated at the beginning of each optimization period. However, the efficiency η may degrade during the optimization period such that the initial efficiency value η₀ becomes increasingly inaccurate over the duration of the optimization period. To account for efficiency degradation during the optimization period, efficiency degrader 913 can decrease the efficiency η by a predetermined amount with each successive time step. For example, efficiency degrader 913 can define the efficiency at each time step i=1 . . . h as follows: η_(i)=η_(i-1)−Δη where η_(i) is the efficiency at time step i, η_(i-1) is the efficiency at time step i−1, and Δη is the degradation in efficiency between consecutive time steps. In some embodiments, this definition of η_(i) is applied to each time step for which B_(main,i)=0 and B_(cap,i)=0. However, if either B_(main,i)=1 or B_(cap,i)=1, the value of η⁷ may be reset to either η_(main) or η_(cap) as previously described.

In some embodiments, the value of Δη is based on a time series of efficiency values calculated by efficiency updater 911. For example, efficiency degrader 913 may record a time series of the initial efficiency values η₀ calculated by efficiency updater 911, where each of the initial efficiency values η₀ represents the empirically-calculated efficiency of connected equipment 610 at a particular time. Efficiency degrader 913 can examine the time series of initial efficiency values η₀ to determine the rate at which the efficiency degrades. For example, if the initial efficiency η₀ at time t₁ is η_(0,1) and the initial efficiency at time t₂ is η_(0.2), efficiency degrader 913 can calculate the rate of efficiency degradation as follows:

$\frac{\Delta\eta}{\Delta\; t} = \frac{\eta_{0,2} - \eta_{0,1}}{t_{2} - t_{1}}$ where

$\frac{\Delta\eta}{\Delta\; t}$ is the rate of efficiency degradation. Efficiency degrader 913 can multiply

$\frac{\Delta\eta}{\Delta\; t}$ by the duration of each time step Δt to calculate the value of Δ_(η)

$\left( {{i.e.},{{\Delta\eta} = {\frac{\Delta\eta}{\Delta\; t}*\Delta\; t}}} \right).$

In some embodiments, efficiency degrader 913 stores the efficiency values over the duration of the optimization period in an array η including an element for each of the h time steps in the optimization period. For example, efficiency degrader 913 can generate the following array: η=[η₁η₂ . . . η_(h)] where the array η has a size of 1×h and each element of the array η includes an efficiency value η_(i) for a particular time step i=1 . . . h of the optimization period. Each element i of the array η may be calculated based on the value of the previous element and the value of Δη (e.g., if B_(main,i)=0 and B_(cap,i)=0) or may be dynamically reset to either η_(main) or η_(cap) (e.g., if B_(main,i)=1 or B_(cap,i)=1.

The logic characterizing the efficiency updating and resetting operations performed by efficiency updater 911 and efficiency degrader 913 can be summarized in the following equations: if B _(main,i)=1→η_(i)=η_(main) if B _(cap,i)=1→η_(i)=η_(cap) if B _(main,i)=0 and B _(cap,i)=0→η_(i)=η_(i-1)−Δη which can be applied as constraints on the high level optimization performed by objective function optimizer 940.

Advantageously, efficiency updater 911 and efficiency degrader 913 can model the efficiency η_(i) of connected equipment 610 at each time step i as a function of the maintenance decisions B_(main,i) and the equipment purchase decisions B_(cap,i). For example, the efficiency η_(i) for a particular device may start at an initial value η₀ at the beginning of the optimization period and may degrade over time such that the efficiency η_(i) decreases with each successive time step i. Performing maintenance on a device may reset the efficiency η_(i) to a higher value immediately after the maintenance is performed. Similarly, purchasing a new device to replace an existing device may reset the efficiency η_(i) to a higher value immediately after the new device is purchased. After being reset, the efficiency η_(i) may continue to degrade over time until the next time at which maintenance is performed or a new device is purchased.

Still referring to FIG. 9, operational cost predictor 910 is shown to include a power consumption estimator 914 and an operational cost calculator 916. Power consumption estimator 914 can be configured to estimate the power consumption P_(op,i) of connected equipment 610 at each time step i of the optimization period. In some embodiments, power consumption estimator 914 estimates the power consumption P_(op,i) as a function of the ideal power consumption P_(ideal,i) calculated by ideal performance calculator 912 and the efficiency η_(i) determined by efficiency degrader 913 and/or efficiency updater 911. For example, power consumption estimator 914 can calculate the power consumption P_(op,i) using the following equation:

$P_{{op},i} = \frac{P_{{ideal},i}}{\eta_{i}}$ where P_(ideal,i) is the power consumption calculated by ideal performance calculator 912 based on the equipment performance curve for the device at the corresponding load point Load_(i), and η_(i) is the operating efficiency of the device at time step i.

In some embodiments, power consumption estimator 914 stores the power consumption values as an array P_(op) including an element for each of the h time steps in the optimization period. For example, power consumption estimator 914 can generate the following array: P _(op)=[P _(op,1) P _(op,2) . . . P _(op,h)]^(T) where the array P_(op) has a size of h×1 and each element of the array P_(op) includes a power consumption value P_(op,i) for a particular time step i=1 . . . h of the optimization period.

Operational cost calculator 916 can be configured to estimate the operational cost of connected equipment 610 over the duration of the optimization period. In some embodiments, operational cost calculator 916 calculates the operational cost during each time step i using the following equation: Cost_(op,i) =C _(op,i) P _(op,i) Δt where P_(op,i) is the predicted power consumption at time step i determined by power consumption estimator 914, C_(op,i) is the cost per unit of energy at time step i determined by energy costs module 915, and Δt is the duration of each time step. Operational cost calculator 916 can sum the operational costs over the duration of the optimization period as follows:

${Cost}_{op} = {\sum\limits_{i = 1}^{h}\;{Cost}_{{op},i}}$ where Cost_(op) is the operational cost term of the objective function J.

In other embodiments, operational cost calculator 916 estimates the operational cost Cost_(op) by multiplying the cost array C_(op) by the power consumption array P_(op) and the duration of each time step Δt as shown in the following equations: Cost_(op) =C _(op) P _(op) Δt Cost_(op)=[C _(op,1) C _(op,2) . . . C _(op,h)][P _(op,1) P _(op,2) . . . P _(op,h)]^(T) Δt Maintenance Cost Predictor

Maintenance cost predictor 920 can be configured to formulate the second term in the objective function J. The second term in the objective function J represents the cost of performing maintenance on connected equipment 610 over the duration of the optimization period and is shown to include two variables or parameters (i.e., C_(main,i) and B_(main,i)). Maintenance cost predictor 920 is shown to include a maintenance estimator 922, a reliability estimator 924, a maintenance cost calculator 926, and a maintenance costs module 928.

Reliability estimator 924 can be configured to estimate the reliability of connected equipment 610 based on the equipment performance information received from connected equipment 610. The reliability may be a statistical measure of the likelihood that connected equipment 610 will continue operating without fault under its current operating conditions. Operating under more strenuous conditions (e.g., high load, high temperatures, etc.) may result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) may result in a higher reliability. In some embodiments, the reliability is based on an amount of time that has elapsed since connected equipment 610 last received maintenance and/or an amount of time that has elapsed since connected equipment 610 was purchased or installed.

In some embodiments, reliability estimator 924 uses the equipment performance information to identify a current operating state of connected equipment 610. The current operating state can be examined by reliability estimator 924 to expose when connected equipment 610 begins to degrade in performance and/or to predict when faults will occur. In some embodiments, reliability estimator 924 estimates a likelihood of various types of failures that could potentially occur in connected equipment 610. The likelihood of each failure may be based on the current operating conditions of connected equipment 610, an amount of time that has elapsed since connected equipment 610 has been installed, and/or an amount of time that has elapsed since maintenance was last performed. In some embodiments, reliability estimator 924 identifies operating states and predicts the likelihood of various failures using the systems and methods described in U.S. patent application Ser. No. 15/188,824 titled “Building Management System With Predictive Diagnostics” and filed Jun. 21, 2016, the entire disclosure of which is incorporated by reference herein.

In some embodiments, reliability estimator 924 receives operating data from a plurality of devices of connected equipment 610 distributed across multiple buildings. The operating data can include, for example, current operating conditions, fault indications, failure times, or other data that characterize the operation and performance of connected equipment 610. Reliability estimator 924 can use the set of operating data to develop a reliability model for each type of equipment. The reliability models can be used by reliability estimator 924 to estimate the reliability of any given device of connected equipment 610 as a function of its current operating conditions and/or other extraneous factors (e.g., time since maintenance was last performed, time since installation or purchase, geographic location, water quality, etc.).

One example of a reliability model which can be used by reliability estimator 924 is shown in the following equation: Reliability_(i)=ƒ(OpCond_(i) ,Δt _(main,i) ,Δt _(cap,i)) where Reliability_(i) is the reliability of connected equipment 610 at time step i, OpCond_(i) are the operating conditions at time step i, Δt_(main,i) is the amount of time that has elapsed between the time at which maintenance was last performed and time step i, and Δt_(cap,i) is the amount of time that has elapsed between the time at which connected equipment 610 was purchased or installed and time step i. Reliability estimator 924 can be configured to identify the current operating conditions OpCond_(i) based on the equipment performance information received as a feedback from connected equipment 610. Operating under more strenuous conditions (e.g., high load, extreme temperatures, etc.) may result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) may result in a higher reliability.

Reliability estimator 924 may determine the amount of time Δt_(main,i) that has elapsed since maintenance was last performed on connected equipment 610 based on the values of the binary decision variables B_(main,i). For each time step i, reliability estimator 924 can examine the corresponding values of B_(main) at time step i and each previous time step (e.g., time steps i−1, i−2, . . . , 1). Reliability estimator 924 can calculate the value of Δt_(main,i) by subtracting the time at which maintenance was last performed (i.e., the most recent time at which B_(main,i)=1) from the time associated with time step i. A long amount of time Δt_(main,i) since maintenance was last performed may result in a lower reliability, whereas a short amount of time since maintenance was last performed may result in a higher reliability.

Similarly, reliability estimator 924 may determine the amount of time Δt_(cap,i) that has elapsed since connected equipment 610 was purchased or installed based on the values of the binary decision variables B_(cap,i). For each time step i, reliability estimator 924 can examine the corresponding values of B_(cap) at time step i and each previous time step (e.g., time steps i−1, i−2, . . . , 1). Reliability estimator 924 can calculate the value of Δt_(cap,i) by subtracting the time at which connected equipment 610 was purchased or installed (i.e., the most recent time at which B_(cap,i)=1) from the time associated with time step i. A long amount of time Δt_(cap,i) since connected equipment 610 was purchased or installed may result in a lower reliability, whereas a short amount of time since connected equipment 610 was purchased or installed may result in a higher reliability.

Reliability estimator 924 can be configured to reset the reliability for a given time step i if the binary decision variables B_(main,i) and B_(cap,i) indicate that maintenance will be performed at that time step and/or new equipment will be purchased at that time step (i.e., B_(main,i)=1 and/or B_(cap,i)=1). For example, if B_(main,i)=1, reliability estimator 924 can be configured to reset the value of Reliability_(i) to Reliability_(main), where Reliability_(main) is the reliability value that is expected to result from the maintenance performed at time step i. Similarly, if B_(cap,i)=1, reliability estimator 924 can be configured to reset the value of Reliability_(i) to Reliability_(cap), where Reliability_(cap) is the reliability value that is expected to result from purchasing a new device to supplement or replace one or more devices of connected equipment 610 performed at time step i. Reliability estimator 924 can dynamically reset the reliability for one or more time steps while the optimization is being performed (e.g., with each iteration of the optimization) based on the values of binary decision variables B_(main,i) and B_(cap,i).

Maintenance estimator 922 can be configured to use the estimated reliability of connected equipment 610 over the duration of the optimization period to determine the probability that connected equipment 610 will require maintenance and/or replacement at each time step of the optimization period. In some embodiments, maintenance estimator 922 is configured to compare the probability that connected equipment 610 will require maintenance at a given time step to a critical value. Maintenance estimator 922 can be configured to set the value of B_(main,i)=1 in response to a determination that the probability that connected equipment 610 will require maintenance at time step i exceeds the critical value. Similarly, maintenance estimator 922 can be configured to compare the probability that connected equipment 610 will require replacement at a given time step to a critical value. Maintenance estimator 922 can be configured to set the value of B_(cap,i)=1 in response to a determination that the probability that connected equipment 610 will require replacement at time step i exceeds the critical value.

In some embodiments, a reciprocal relationship exists between the reliability of connected equipment 610 and the values of the binary decision variables B_(main,i) and B_(cap,i). In other words, the reliability of connected equipment 610 can affect the values of the binary decision variables B_(main,i) and B_(cap,i) selected in the optimization, and the values of the binary decision variables B_(main,i) and B_(cap,i) can affect the reliability of connected equipment 610. Advantageously, the optimization performed by objective function optimizer 940 can identify the optimal values of the binary decision variables B_(main,i) and B_(cap,i) while accounting for the reciprocal relationship between the binary decision variables B_(main,i) and B_(cap,i) and the reliability of connected equipment 610.

In some embodiments, maintenance estimator 922 generates a matrix B_(main) of the binary maintenance decision variables. The matrix B_(main) may include a binary decision variable for each of the different maintenance activities that can be performed at each time step of the optimization period. For example, maintenance estimator 922 can generate the following matrix:

$B_{main} = \begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix}$ where the matrix B_(main) has a size of m×h and each element of the matrix B_(main) includes a binary decision variable for a particular maintenance activity at a particular time step of the optimization period. For example, the value of the binary decision variable B_(main,j,i) indicates whether the jth maintenance activity will be performed during the ith time step of the optimization period.

Still referring to FIG. 9, maintenance cost predictor 920 is shown to include a maintenance costs module 928 and a maintenance cost calculator 926. Maintenance costs module 928 can be configured to determine costs C_(main,i) associated with performing various types of maintenance on connected equipment 610. Maintenance costs module 928 can receive a set of maintenance costs from an external system or device (e.g., a database, a user device, etc.). In some embodiments, the maintenance costs define the economic cost (e.g., $) of performing various types of maintenance. Each type of maintenance activity may have a different economic cost associated therewith. For example, the maintenance activity of changing the oil in a chiller compressor may incur a relatively small economic cost, whereas the maintenance activity of completely disassembling the chiller and cleaning all of the chilled water tubes may incur a significantly larger economic cost.

Maintenance costs module 928 can use the maintenance costs to define the values of C_(main,i) in objective function J. In some embodiments, maintenance costs module 928 stores the maintenance costs as an array C_(main) including a cost element for each of the maintenance activities that can be performed. For example, maintenance costs module 928 can generate the following array: C _(main)=[C _(main,i) C _(main,2) . . . C _(main,m)] where the array C_(main) has a size of 1×m and each element of the array C_(main) includes a maintenance cost value C_(main,j) for a particular maintenance activity j=1 . . . m.

Some maintenance activities may be more expensive than other. However, different types of maintenance activities may result in different levels of improvement to the efficiency η and/or the reliability of connected equipment 610. For example, merely changing the oil in a chiller may result in a minor improvement in efficiency η and/or a minor improvement in reliability, whereas completely disassembling the chiller and cleaning all of the chilled water tubes may result in a significantly greater improvement to the efficiency η and/or the reliability of connected equipment 610. Accordingly, multiple different levels of post-maintenance efficiency (i.e., η_(main)) and post-maintenance reliability (i.e., Reliability_(main)) may exist. Each level of η_(main) and Reliability_(main) may correspond to a different type of maintenance activity.

In some embodiments, maintenance estimator 922 stores each of the different levels of η_(main) and Reliability_(main) in a corresponding array. For example, the parameter η_(main) can be defined as an array η_(main) with an element for each of the m different types of maintenance activities. Similarly, the parameter Reliability_(main) can be defined as an array Reliability_(main) with an element for each of the m different types of maintenance activities.

Examples of these arrays are shown in the following equations: η_(main)=[η_(main,1)η_(main,2) . . . η_(main,m)] Reliability_(main)=[Reliability_(main,1) Reliability_(main,2) . . . Reliability_(main,m)] where the array η_(main) has a size of 1×m and each element of the array η_(main) includes a post-maintenance efficiency value η_(main,j) for a particular maintenance activity. Similarly, the array Reliability_(main) has a size of 1×m and each element of the array Reliability_(main) includes a post-maintenance reliability value Reliability_(main,j) for a particular maintenance activity.

In some embodiments, efficiency updater 911 identifies the maintenance activity associated with each binary decision variable B_(main,j,i) and resets the efficiency η to the corresponding post-maintenance efficiency level η_(main,j) if B_(main,j,i)=1. Similarly, reliability estimator 924 can identify the maintenance activity associated with each binary decision variable B_(main,j,i) and can reset the reliability to the corresponding post-maintenance reliability level Reliability_(main,j) if B_(main,j,i)=1.

Maintenance cost calculator 926 can be configured to estimate the maintenance cost of connected equipment 610 over the duration of the optimization period. In some embodiments, maintenance cost calculator 926 calculates the maintenance cost during each time step i using the following equation: Cost_(main,i) =C _(main,i) B _(main,i) where C_(main,i) is an array of maintenance costs including an element for each of the m different types of maintenance activities that can be performed at time step i and B_(main,i) is an array of binary decision variables indicating whether each of the m maintenance activities will be performed at time step i. Maintenance cost calculator 926 can sum the maintenance costs over the duration of the optimization period as follows:

${Cost}_{main} = {\sum\limits_{i = 1}^{h}{Cost}_{{main},i}}$ where Cost_(main) is the maintenance cost term of the objective function J.

In other embodiments, maintenance cost calculator 926 estimates the maintenance cost Cost_(main) by multiplying the maintenance cost array C_(main) by the matrix of binary decision variables B_(main) as shown in the following equations:

  Cost_(main) = C_(main)B_(main) ${Cost}_{main} = {\left\lbrack {C_{{main},1}\mspace{25mu} C_{{main},2}\mspace{20mu}\ldots\mspace{20mu} C_{{main},m}} \right\rbrack{\quad\begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix}}}$ Capital Cost Predictor

Capital cost predictor 930 can be configured to formulate the third term in the objective function J. The third term in the objective function J represents the cost of purchasing new devices of connected equipment 610 over the duration of the optimization period and is shown to include two variables or parameters (i.e., C_(cap,i) and B_(cap,i)). Capital cost predictor 930 is shown to include a purchase estimator 932, a reliability estimator 934, a capital cost calculator 936, and a capital costs module 938.

Reliability estimator 934 can include some or all of the features of reliability estimator 924, as described with reference to maintenance cost predictor 920. For example, reliability estimator 934 can be configured to estimate the reliability of connected equipment 610 based on the equipment performance information received from connected equipment 610. The reliability may be a statistical measure of the likelihood that connected equipment 610 will continue operating without fault under its current operating conditions. Operating under more strenuous conditions (e.g., high load, high temperatures, etc.) may result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) may result in a higher reliability. In some embodiments, the reliability is based on an amount of time that has elapsed since connected equipment 610 last received maintenance and/or an amount of time that has elapsed since connected equipment 610 was purchased or installed. Reliability estimator 934 can include some or all of the features and/or functionality of reliability estimator 924, as previously described.

Purchase estimator 932 can be configured to use the estimated reliability of connected equipment 610 over the duration of the optimization period to determine the probability that new devices of connected equipment 610 will be purchased at each time step of the optimization period. In some embodiments, purchase estimator 932 is configured to compare the probability that new devices of connected equipment 610 will be purchased at a given time step to a critical value. Purchase estimator 932 can be configured to set the value of B_(cap,i)=1 in response to a determination that the probability that connected equipment 610 will be purchased at time step i exceeds the critical value.

In some embodiments, purchase estimator 932 generates a matrix B_(cap) of the binary capital decision variables. The matrix B_(cap) may include a binary decision variable for each of the different capital purchases that can be made at each time step of the optimization period. For example, purchase estimator 932 can generate the following matrix:

$B_{cap} = \begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}$ where the matrix B_(cap) has a size of p×h and each element of the matrix B_(cap) includes a binary decision variable for a particular capital purchase at a particular time step of the optimization period. For example, the value of the binary decision variable B_(cap,k,i) indicates whether the kth capital purchase will be made during the ith time step of the optimization period.

Still referring to FIG. 9, capital cost predictor 930 is shown to include a capital costs module 938 and a capital cost calculator 936. Capital costs module 938 can be configured to determine costs C_(cap,i) associated with various capital purchases (i.e., purchasing one or more new devices of connected equipment 610). Capital costs module 938 can receive a set of capital costs from an external system or device (e.g., a database, a user device, etc.). In some embodiments, the capital costs define the economic cost (e.g., $) of making various capital purchases. Each type of capital purchase may have a different economic cost associated therewith. For example, purchasing a new temperature sensor may incur a relatively small economic cost, whereas purchasing a new chiller may incur a significantly larger economic cost.

Capital costs module 938 can use the purchase costs to define the values of C_(cap,i) in objective function J. In some embodiments, capital costs module 938 stores the capital costs as an array C_(cap) including a cost element for each of the capital purchases that can be made. For example, capital costs module 938 can generate the following array: C _(cap)=[C _(cap,1) C _(cap,2) . . . C _(cap,p)] where the array C_(cap) has a size of 1×p and each element of the array C_(cap) includes a cost value C_(cap,k) for a particular capital purchase k=1 . . . p.

Some capital purchases may be more expensive than other. However, different types of capital purchases may result in different levels of improvement to the efficiency η and/or the reliability of connected equipment 610. For example, purchasing a new sensor to replace an existing sensor may result in a minor improvement in efficiency η and/or a minor improvement in reliability, whereas purchasing a new chiller and control system may result in a significantly greater improvement to the efficiency η and/or the reliability of connected equipment 610. Accordingly, multiple different levels of post-purchase efficiency (i.e., η_(cap)) and post-purchase reliability (i.e., Reliability_(cap)) may exist. Each level of η_(cap) and Reliability_(cap) may correspond to a different type of capital purchase.

In some embodiments, purchase estimator 932 stores each of the different levels of η_(cap) and Reliability_(cap) in a corresponding array. For example, the parameter η_(cap) can be defined as an array η_(cap) with an element for each of the p different types of capital purchases which can be made. Similarly, the parameter Reliability_(cap) can be defined as an array Reliability_(cap) with an element for each of the p different types of capital purchases that can be made. Examples of these arrays are shown in the following equations: η_(cap)=[η_(cap,1)η_(cap,2) . . . η_(cap,p)] Reliability_(cap)=[Reliability_(cap,1) Reliability_(cap,2) . . . Reliability_(cap,p)] where the array η_(cap) has a size of 1×p and each element of the array η_(cap) includes a post-purchase efficiency value η_(cap,k) for a particular capital purchase k. Similarly, the array Reliability_(cap) has a size of 1×p and each element of the array Reliability_(cap) includes a post-purchase reliability value Reliability_(cap,k) for a particular capital purchase k.

In some embodiments, efficiency updater 911 identifies the capital purchase associated with each binary decision variable B_(main,k,i) and resets the efficiency η to the corresponding post-purchase efficiency level η_(cap,k) if B_(cap,k,i)=1. Similarly, reliability estimator 924 can identify the capital purchase associated with each binary decision variable B_(cap,k,i) and can reset the reliability to the corresponding post-purchase reliability level Reliability_(cap,k) if B_(main,k,i)=1.

Capital cost calculator 936 can be configured to estimate the capital cost of connected equipment 610 over the duration of the optimization period. In some embodiments, capital cost calculator 936 calculates the capital cost during each time step i using the following equation: Cost_(cap,i) =C _(cap,i) B _(cap,i) where C_(cap,i) is an array of capital purchase costs including an element for each of the p different capital purchases that can be made at time step i and B_(cap,i) is an array of binary decision variables indicating whether each of the p capital purchases will be made at time step i. Capital cost calculator 936 can sum the capital costs over the duration of the optimization period as follows:

${Cost}_{cap} = {\sum\limits_{i = 1}^{h}{Cost}_{{cap},i}}$ where Cost_(cap) is the capital cost term of the objective function J.

In other embodiments, capital cost calculator 936 estimates the capital cost Cost_(cap) by multiplying the capital cost array C_(cap) by the matrix of binary decision variables B_(cap) as shown in the following equations:

  Cost_(cap) = C_(cap)B_(cap) ${Cost}_{cap} = {\left\lbrack {C_{{cap},1}\mspace{25mu} C_{{cap},2}\mspace{20mu}\ldots\mspace{20mu} C_{{cap},p}} \right\rbrack{\quad\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}}}$ Objective Function Optimizer

Still referring to FIG. 9, high level optimizer 832 is shown to include an objective function generator 935 and an objective function optimizer 940. Objective function generator 935 can be configured to generate the objective function J by summing the operational cost term, the maintenance cost term, and the capital cost term formulated by cost predictors 910, 920, and 930. One example of an objective function which can be generated by objective function generator 935 is shown in the following equation:

$J = {{\sum\limits_{i = 1}^{h}{C_{{op},i}P_{{op},i}\Delta\; t}} + {\sum\limits_{i = 1}^{h}{C_{{main},i}B_{{main},i}}} + {\sum\limits_{i = 1}^{h}{C_{{cap},i}P_{{cap},i}}}}$ where C_(op,i) is the cost per unit of energy (e.g., $/kWh) consumed by connected equipment 610 at time step i of the optimization period, P_(op,i) is the power consumption (e.g., kW) of connected equipment 610 at time step i, Δt is the duration of each time step i, C_(main,i) is the cost of maintenance performed on connected equipment 610 at time step i, B_(main,i) is a binary variable that indicates whether the maintenance is performed, C_(cap,i) is the capital cost of purchasing a new device of connected equipment 610 at time step i, B_(cap,i) is a binary variable that indicates whether the new device is purchased, and h is the duration of the horizon or optimization period over which the optimization is performed.

Another example of an objective function which can be generated by objective function generator 935 is shown in the following equation:

      J = C_(op)P_(op)Δ t + C_(main)B_(main) + C_(cap)B_(cap) $J = {{{\left\lbrack {C_{{op},1}\mspace{20mu} C_{{op},2}\mspace{14mu}\ldots\mspace{14mu} C_{{op},h}} \right\rbrack\left\lbrack {P_{{op},1}\mspace{20mu} P_{{op},2}\mspace{14mu}\ldots\mspace{20mu} P_{{op},h}} \right\rbrack}^{T}\Delta\; t} + {\quad{\left\lbrack {C_{{main},1}\mspace{25mu} C_{{main},2}\mspace{20mu}\ldots\mspace{20mu} C_{{main},m}} \right\rbrack{\quad{\begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix} + {\quad{\left\lbrack {C_{{cap},1}\mspace{25mu} C_{{cap},2}\mspace{20mu}\ldots\mspace{20mu} C_{{cap},p}} \right\rbrack{\quad\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}}}}}}}}}$ where the array C_(op) includes an energy cost value C_(op,i) for a particular time step i=1 . . . h of the optimization period, the array P_(op) includes a power consumption value P_(op,i) for a particular time step i=1 . . . h of the optimization period, each element of the array C_(main) includes a maintenance cost value C_(main,j) for a particular maintenance activity j=1 . . . m, each element of the matrix B_(main) includes a binary decision variable for a particular maintenance activity j=1 . . . m at a particular time step i=1 . . . h of the optimization period, each element of the array C_(cap) includes a capital cost value C_(cap,k) for a particular capital purchase k=1 . . . p, and each element of the matrix B_(cap) includes a binary decision variable for a particular capital purchase k=1 . . . p at a particular time step i=1 . . . h of the optimization period.

Objective function generator 935 can be configured to impose constraints on one or more variables or parameters in the objective function J. The constraints can include any of the equations or relationships described with reference to operational cost predictor 910, maintenance cost predictor 920, and capital cost predictor 930. For example, objective function generator 935 can impose a constraint which defines the power consumption values P_(op,i) for one or more devices of connected equipment 610 as a function of the ideal power consumption P_(ideal,i) and the efficiency η_(i) (e.g., P_(op,i)=P_(ideal,i)/η_(i)). Objective function generator 935 can impose a constraint which defines the efficiency η_(i) as a function of the binary decision variables B_(main,i) and B_(cap,i), as described with reference to efficiency updater 911 and efficiency degrader 913. Objective function generator 935 can impose a constraint which constrains the binary decision variables B_(main,i) and B_(cap,i) to a value of either zero or one and defines the binary decision variables B_(main,i) and B_(cap,i) as a function of the reliability Reliability_(i) of connected equipment 610, as described with reference to maintenance estimator 922 and purchase estimator 932. Objective function generator 935 can impose a constraint which defines the reliability Reliability_(i) of connected equipment 610 as a function of the equipment performance information (e.g., operating conditions, run hours, etc.) as described with reference to reliability estimators 924 and 934.

Objective function optimizer 940 can optimize the objective function J to determine the optimal values of the binary decision variables B_(main,i) and B_(cap,i) over the duration of the optimization period. Objective function optimizer 940 can use any of a variety of optimization techniques to formulate and optimize the objective function J. For example, objective function optimizer 940 can use integer programming, mixed integer linear programming, stochastic optimization, convex programming, dynamic programming, or any other optimization technique to formulate the objective function J, define the constraints, and perform the optimization. These and other optimization techniques are known in the art and will not be described in detail here.

In some embodiments, objective function optimizer 940 uses mixed integer stochastic optimization to optimize the objective function J. In mixed integer stochastic optimization, some of the variables in the objective function J can be defined as functions of random variables or probabilistic variables. For example, the decision variables B_(main,i) and B_(cap,i) can be defined as binary variables that have probabilistic values based on the reliability of connected equipment 610. Low reliability values may increase the probability that the binary decision variables B_(main,i) and B_(cap,i) will have a value of one (e.g., B_(main,i)=1 and B_(cap,i)=1), whereas high reliability values may increase the probability that the binary decision variables B_(main,i) and B_(cap,i) will have a value of zero (e.g., B_(main,i)=0 and B_(cap,i)=0). In some embodiments, maintenance estimator 922 and purchase estimator 932 use a mixed integer stochastic technique to define the values of the binary decision variables B_(main,i) and B_(cap,i) as a probabilistic function of the reliability of connected equipment 610.

As discussed above, the objective function J may represent the predicted cost of operating, maintaining, and purchasing one or more devices of connected equipment 610 over the duration of the optimization period. In some embodiments, objective function optimizer 940 is configured to project these costs back to a particular point in time (e.g., the current time) to determine the net present value (NPV) of the one or more devices of connected equipment 610 at a particular point in time. For example, objective function optimizer 940 can project each of the costs in objective function J back to the current time using the following equation:

${NPV}_{cost} = {\sum\limits_{i = 1}^{h}\frac{{Cost}_{i}}{\left( {1 + r} \right)^{i}}}$ where r is the interest rate, Cost_(i) is the cost incurred during time step i of the optimization period, and NPV_(cost) is the net present value (i.e., the present cost) of the total costs incurred over the duration of the optimization period. In some embodiments, objective function optimizer 940 optimizes the net present value NPV_(cost) to determine the NPV of one or more devices of connected equipment 610 at a particular point in time.

As discussed above, one or more variables or parameters in the objective function J can be updated dynamically based on closed-loop feedback from connected equipment 610. For example, the equipment performance information received from connected equipment 610 can be used to update the reliability and/or the efficiency of connected equipment 610. Objective function optimizer 940 can be configured to optimize the objective function J periodically (e.g., once per day, once per week, once per month, etc.) to dynamically update the predicted cost and/or the net present value NPV_(cost) based on the closed-loop feedback from connected equipment 610.

In some embodiments, objective function optimizer 940 generates optimization results. The optimization results may include the optimal values of the decision variables in the objective function J for each time step i in the optimization period. The optimization results include operating decisions, equipment maintenance decisions, and/or equipment purchase decisions for each device of connected equipment 610. In some embodiments, the optimization results optimize the economic value of operating, maintaining, and purchasing connected equipment 610 over the duration of the optimization period. In some embodiments, the optimization results optimize the net present value of one or more devices of connected equipment 610 at a particular point in time. The optimization results may cause BMS 606 to activate, deactivate, or adjust a setpoint for connected equipment 610 in order to achieve the optimal values of the decision variables specified in the optimization results.

In some embodiments, MPM system 602 uses the optimization results to generate equipment purchase and maintenance recommendations. The equipment purchase and maintenance recommendations may be based on the optimal values for the binary decision variables B_(main,i) and B_(cap,i) determined by optimizing the objective function J. For example, a value of B_(main,25)=1 for a particular device of connected equipment 610 may indicate that maintenance should be performed on that device at the 25^(th) time step of the optimization period, whereas a value of B_(main,25)=0 may indicate that the maintenance should not be performed at that time step. Similarly, a value of B_(cap,25)=1 may indicate that a new device of connected equipment 610 should be purchased at the 25^(th) time step of the optimization period, whereas a value of B_(cap,25)=0 may indicate that the new device should not be purchased at that time step.

In some embodiments, the equipment purchase and maintenance recommendations are provided to building 10 (e.g., to BMS 606) and/or to client devices 448. An operator or building owner can use the equipment purchase and maintenance recommendations to assess the costs and benefits of performing maintenance and purchasing new devices. In some embodiments, the equipment purchase and maintenance recommendations are provided to service technicians 620. Service technicians 620 can use the equipment purchase and maintenance recommendations to determine when customers should be contacted to perform service or replace equipment.

Model Predictive Maintenance Process

Referring now to FIG. 10, a flowchart of a model predictive maintenance process 1000 is shown, according to an exemplary embodiment. Process 1000 can be performed by one or more components of building system 600. In some embodiments, process 1000 is performed by MPM system 602, as described with reference to FIGS. 6-9.

Process 1000 is shown to include operating building equipment to affect a variable state or condition of a building (step 1002) and receiving equipment performance information as feedback from the building equipment (step 1004). The building equipment can include type of equipment which can be used to monitor and/or control a building (e.g., connected equipment 610). For example, the building equipment can include chillers, AHUs, boilers, batteries, heaters, economizers, valves, actuators, dampers, cooling towers, fans, pumps, lighting equipment, security equipment, refrigeration equipment, or any other type of equipment in a building system or building management system. The building equipment can include any of the equipment of HVAC system 100, waterside system 200, airside system 300, BMS 400, and/or BMS 500, as described with reference to FIGS. 1-5. The equipment performance information can include samples of monitored variables (e.g., measured temperature, measured pressure, measured flow rate, power consumption, etc.), current operating conditions (e.g., heating or cooling load, current operating state, etc.), fault indications, or other types of information that characterize the performance of the building equipment.

Process 1000 is shown to include estimating an efficiency and reliability of the building equipment as a function of the equipment performance information (step 1006). In some embodiments, step 1006 is performed by efficiency updater 911 and reliability estimators 924, 926 as described with reference to FIG. 9. Step 1006 can include using the equipment performance information to determine the efficiency η of the building equipment under actual operating conditions. In some embodiments, the efficiency η_(i) represents the ratio of the ideal power consumption P_(ideal) of the building equipment to the actual power consumption P_(actual) of the building equipment, as shown in the following equation:

$\eta = \frac{P_{ideal}}{P_{actual}}$ where P_(ideal) is the ideal power consumption of the building equipment as defined by the performance curve for the building equipment and P_(actual) is the actual power consumption of the building equipment. In some embodiments, step 1006 includes using the equipment performance information collected in step 1002 to identify the actual power consumption value P_(actual). Step 1006 can include using the actual power consumption P_(actual) in combination with the ideal power consumption P_(ideal) to calculate the efficiency η.

Step 1006 can include periodically updating the efficiency η to reflect the current operating efficiency of the building equipment. For example, step 1006 can include calculating the efficiency η of the building equipment once per day, once per week, once per year, or at any other interval as can be suitable to capture changes in the efficiency η over time. Each value of the efficiency η can be based on corresponding values of P_(ideal) and P_(actual) at the time the efficiency η is calculated. In some embodiments, step 1006 includes updating the efficiency η each time the high level optimization process is performed (i.e., each time the objective function J is optimized). The efficiency value calculated in step 1006 can be stored in memory 810 as an initial efficiency value η₀, where the subscript 0 denotes the value of the efficiency η at or before the beginning of the optimization period (e.g., at time step 0).

Step 1006 can include predicting the efficiency η_(i) of the building equipment at each time step i of the optimization period. The initial efficiency η₀ at the beginning of the optimization period can degrade over time as the building equipment degrade in performance. For example, the efficiency of a chiller can degrade over time as a result of the chilled water tubes becoming dirty and reducing the heat transfer coefficient of the chiller. Similarly, the efficiency of a battery can decrease over time as a result of degradation in the physical or chemical components of the battery. Step 1006 can account for such degradation by incrementally reducing the efficiency η_(i) over the duration of the optimization period.

In some embodiments, the initial efficiency value η₀ is updated at the beginning of each optimization period. However, the efficiency η can degrade during the optimization period such that the initial efficiency value η₀ becomes increasingly inaccurate over the duration of the optimization period. To account for efficiency degradation during the optimization period, step 1006 can include decreasing the efficiency η by a predetermined amount with each successive time step. For example, step 1006 can include defining the efficiency at each time step i=1 . . . h as follows: η_(i)=η_(i-1)−Δη where η_(i) is the efficiency at time step i, η_(i-1) is the efficiency at time step i−1, and Δη is the degradation in efficiency between consecutive time steps. In some embodiments, this definition of η_(i) is applied to each time step for which B_(main,i)=0 and B_(cap,i)=0. However, if either B_(main,i)=1 or B_(cap,i)=1, the value of r can be reset to either η_(main) or η_(cap) in step 1018.

In some embodiments, the value of Δη is based on a time series of efficiency values. For example, step 1006 can include recording a time series of the initial efficiency values η₀, where each of the initial efficiency values η₀ represents the empirically-calculated efficiency of the building equipment at a particular time. Step 1006 can include examining the time series of initial efficiency values η₀ to determine the rate at which the efficiency degrades. For example, if the initial efficiency 770 at time t₁ is η_(0,1) and the initial efficiency at time t₂ is η_(0.2), the rate of efficiency degradation can be calculated as follows:

$\frac{\Delta\;\eta}{\Delta\; t} = \frac{\eta_{0,2} - \eta_{0,1}}{t_{2} - t_{1}}$ where

$\frac{\Delta\;\eta}{\Delta\; t}$ is the rate of efficiency degradation. Step 1006 can include multiplying

$\frac{\Delta\;\eta}{\Delta\; t}$ by the duration of each time step Δt to calculate the value of Δη

$\left( {{i.e.},{{\Delta\;\eta} = {\frac{\Delta\;\eta}{\Delta\; t}*\Delta\; t}}} \right).$

Step 1006 can include estimating the reliability of the building equipment based on the equipment performance information received in step 1004. The reliability can be a statistical measure of the likelihood that the building equipment will continue operating without fault under its current operating conditions. Operating under more strenuous conditions (e.g., high load, high temperatures, etc.) can result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) can result in a higher reliability. In some embodiments, the reliability is based on an amount of time that has elapsed since the building equipment last received maintenance and/or an amount of time that has elapsed since the building equipment were purchased or installed.

In some embodiments, step 1006 includes using the equipment performance information to identify a current operating state of the building equipment. The current operating state can be examined to expose when the building equipment begin to degrade in performance and/or to predict when faults will occur. In some embodiments, step 1006 includes estimating a likelihood of various types of failures that could potentially occur the building equipment. The likelihood of each failure can be based on the current operating conditions of the building equipment, an amount of time that has elapsed since the building equipment have been installed, and/or an amount of time that has elapsed since maintenance was last performed. In some embodiments, step 1006 includes identifying operating states and predicts the likelihood of various failures using the systems and methods described in U.S. patent application Ser. No. 15/188,824 titled “Building Management System With Predictive Diagnostics” and filed Jun. 21, 2016, the entire disclosure of which is incorporated by reference herein.

In some embodiments, step 1006 includes receiving operating data from building equipment distributed across multiple buildings. The operating data can include, for example, current operating conditions, fault indications, failure times, or other data that characterize the operation and performance of the building equipment. Step 1006 can include using the set of operating data to develop a reliability model for each type of equipment. The reliability models can be used in step 1006 to estimate the reliability of any given device of the building equipment as a function of its current operating conditions and/or other extraneous factors (e.g., time since maintenance was last performed, time since installation or purchase, geographic location, water quality, etc.).

One example of a reliability model which can be used in step 1006 is shown in the following equation: Reliability_(i)=ƒ(OpCond_(i) ,Δt _(main,i) ,Δt _(cap,i)) where Reliability_(i) is the reliability of the building equipment at time step i, OpCond_(i) are the operating conditions at time step i, Δt_(main,i) is the amount of time that has elapsed between the time at which maintenance was last performed and time step i, and Δt_(cap,i) is the amount of time that has elapsed between the time at which the building equipment were purchased or installed and time step i. Step 1006 can include identifying the current operating conditions OpCond_(i) based on the equipment performance information received as a feedback from the building equipment. Operating under more strenuous conditions (e.g., high load, extreme temperatures, etc.) can result in a lower reliability, whereas operating under less strenuous conditions (e.g., low load, moderate temperatures, etc.) can result in a higher reliability.

Still referring to FIG. 10, process 1000 is shown to include predicting an energy consumption of the building equipment over an optimization period as a function of the estimated efficiency (step 1008). In some embodiments, step 1008 is performed by ideal performance calculator 912 and/or power consumption estimator, as described with reference to FIG. 9. Step 1008 can include receiving load predictions Load_(i) from load/rate predictor 822 and performance curves from low level optimizer 834. As discussed above, the performance curves can define the ideal power consumption P_(ideal) of the building equipment a function of the heating or cooling load on the device or set of devices. For example, the performance curve for the building equipment can be defined by the following equation: P _(ideal,i)=ƒ(Load_(i)) where P_(ideal,i) is the ideal power consumption (e.g., kW) of the building equipment at time step i and Load_(i) is the load (e.g., tons cooling, kW heating, etc.) on the building equipment at time step i. The ideal power consumption P_(ideal,i) can represent the power consumption of the building equipment assuming they operate at perfect efficiency. Step 1008 can include using the performance curve for the building equipment to identify the value of P_(ideal,i) that corresponds to the load point Load_(i) for the building equipment at each time step of the optimization period.

In some embodiments, step 1008 includes estimating the power consumption P_(op,i) as a function of the ideal power consumption P_(ideal,i) and the efficiency η_(i) of the building equipment. For example, step 1008 can include calculating the power consumption P_(op,i) using the following equation:

$\begin{matrix} {P_{{op},i} = \frac{P_{{ideal},i}}{\eta_{i}}} & \; \end{matrix}$ where P_(ideal,i) is the power consumption based on the equipment performance curve for the building equipment at the corresponding load point Load_(i), and η_(i) is the operating efficiency of the building equipment at time step i.

Still referring to FIG. 10, process 1000 is shown to include defining a cost Cost_(op) of operating the building equipment over the optimization period as a function of the predicted energy consumption (step 1010). In some embodiments, step 1010 is performed by operational cost calculator 916, as described with reference to FIG. 9. Step 1010 can include calculating the operational cost during each time step i using the following equation: Cost_(op,i) =C _(op,i) P _(op,i) Δt where P_(op,i) is the predicted power consumption at time step i determined in step 1008, C_(op,i) is the cost per unit of energy at time step i, and Δt is the duration of each time step. Step 1010 can include summing the operational costs over the duration of the optimization period as follows:

${Cost}_{op} = {\sum\limits_{i = 1}^{h}{Cost}_{{op},i}}$ where Cost_(op) is the operational cost term of the objective function J.

In other embodiments, step 1010 can include calculating the operational cost Cost_(op) by multiplying the cost array C_(op) by the power consumption array P_(op) and the duration of each time step Δt as shown in the following equations: Cost_(op) =C _(op) P _(op) Δt Cost_(op)=[C _(op,1) C _(op,2) . . . C _(op,h)][P _(op,1) P _(op,2) . . . P _(op,h)]^(T) Δt where the array C_(op) includes an energy cost value C_(op,i) for a particular time step i=1 . . . h of the optimization period, the array P_(op) includes a power consumption value P_(op,i) for a particular time step i=1 . . . h of the optimization period.

Still referring to FIG. 10, process 1000 is shown to include defining a cost of performing maintenance on the building equipment over the optimization period as a function of the estimated reliability (step 1012). Step 1012 can be performed by maintenance cost predictor 920, as described with reference to FIG. 9. Step 1012 can include using the estimated reliability of the building equipment over the duration of the optimization period to determine the probability that the building equipment will require maintenance and/or replacement at each time step of the optimization period. In some embodiments, step 1012 includes comparing the probability that the building equipment will require maintenance at a given time step to a critical value. Step 1012 can include setting the value of B_(main,i)=1 in response to a determination that the probability that the building equipment will require maintenance at time step i exceeds the critical value. Similarly, step 1012 can include comparing the probability that the building equipment will require replacement at a given time step to a critical value. Step 1012 can include setting the value of B_(cap,i)=1 in response to a determination that the probability that the building equipment will require replacement at time step i exceeds the critical value.

Step 1012 can include determining the costs C_(main,i) associated with performing various types of maintenance on the building equipment. Step 1012 can include receiving a set of maintenance costs from an external system or device (e.g., a database, a user device, etc.). In some embodiments, the maintenance costs define the economic cost (e.g., $) of performing various types of maintenance. Each type of maintenance activity can have a different economic cost associated therewith. For example, the maintenance activity of changing the oil in a chiller compressor can incur a relatively small economic cost, whereas the maintenance activity of completely disassembling the chiller and cleaning all of the chilled water tubes can incur a significantly larger economic cost. Step 1012 can include using the maintenance costs to define the values of C_(main,i) in objective function J.

Step 1012 can include estimating the maintenance cost of the building equipment over the duration of the optimization period. In some embodiments, step 1012 includes calculating the maintenance cost during each time step i using the following equation: Cost_(main,i) =C _(main,i) B _(main,i) where C_(main,i) is an array of maintenance costs including an element for each of the m different types of maintenance activities that can be performed at time step i and B_(main,i) is an array of binary decision variables indicating whether each of the m maintenance activities will be performed at time step i. Step 1012 can include summing the maintenance costs over the duration of the optimization period as follows:

${Cost}_{main} = {\sum\limits_{i = 1}^{h}{Cost}_{{main},i}}$ where Cost_(main) is the maintenance cost term of the objective function J.

In other embodiments, step 1012 includes estimating the maintenance cost Cost_(main) by multiplying the maintenance cost array C_(main) by the matrix of binary decision variables B_(main) as shown in the following equations:

  Cost_(main) = C_(main)B_(main) ${Cost}_{main} = {\left\lbrack {C_{{main},1}\mspace{20mu} C_{{main},2}\mspace{14mu}\ldots\mspace{14mu} C_{{main},m}} \right\rbrack{\quad\begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix}}}$ where each element of the array C_(main) includes a maintenance cost value C_(main,j) for a particular maintenance activity j=1 . . . m and each element of the matrix B_(main) includes a binary decision variable for a particular maintenance activity j=1 . . . m at a particular time step i=1 . . . h of the optimization period.

Still referring to FIG. 10, process 1000 is shown to include defining a cost Cost_(cap) of purchasing or replacing the building equipment over the optimization period as a function of the estimated reliability (step 1014). Step 1014 can be performed by capital cost predictor 930, as described with reference to FIG. 9. In some embodiments, step 1014 includes using the estimated reliability of the building equipment over the duration of the optimization period to determine the probability that new devices of the building equipment will be purchased at each time step of the optimization period. In some embodiments, step 1014 includes comparing the probability that new devices of the building equipment will be purchased at a given time step to a critical value. Step 1014 can include setting the value of B_(cap,i)=1 in response to a determination that the probability that the building equipment will be purchased at time step i exceeds the critical value.

Step 1014 can include determining the costs C_(cap,i) associated with various capital purchases (i.e., purchasing one or more new devices of the building equipment). Step 1014 can include receiving a set of capital costs from an external system or device (e.g., a database, a user device, etc.). In some embodiments, the capital costs define the economic cost (e.g., $) of making various capital purchases. Each type of capital purchase can have a different economic cost associated therewith. For example, purchasing a new temperature sensor can incur a relatively small economic cost, whereas purchasing a new chiller can incur a significantly larger economic cost. Step 1014 can include using the purchase costs to define the values of C_(cap,i) in objective function J.

Some capital purchases can be more expensive than other. However, different types of capital purchases can result in different levels of improvement to the efficiency η and/or the reliability of the building equipment. For example, purchasing a new sensor to replace an existing sensor can result in a minor improvement in efficiency η and/or a minor improvement in reliability, whereas purchasing a new chiller and control system can result in a significantly greater improvement to the efficiency η and/or the reliability of the building equipment. Accordingly, multiple different levels of post-purchase efficiency (i.e., η_(cap)) and post-purchase reliability (i.e., Reliability_(cap)) can exist. Each level of η_(cap) and Reliability_(cap) can correspond to a different type of capital purchase.

Step 1014 can include estimating the capital cost of the building equipment over the duration of the optimization period. In some embodiments, step 1014 includes calculating the capital cost during each time step i using the following equation: Cost_(cap,i) =C _(cap,i) B _(cap,i) where C_(cap,i) is an array of capital purchase costs including an element for each of the p different capital purchases that can be made at time step i and B_(cap,i) is an array of binary decision variables indicating whether each of the p capital purchases will be made at time step i. Step 1014 can include summing the capital costs over the duration of the optimization period as follows:

${Cost}_{cap} = {\sum\limits_{i = 1}^{h}{Cost}_{{cap},i}}$ where Cost_(cap) is the capital cost term of the objective function J.

In other embodiments, step 1014 includes estimating the capital cost Cost_(cap) by multiplying the capital cost array C_(cap) by the matrix of binary decision variables B_(cap) as shown in the following equations:

  Cost_(cap) = C_(cap)B_(cap) ${Cost}_{cap} = {\left\lbrack {C_{{cap},1}\mspace{20mu} C_{{cap},2}\mspace{14mu}\ldots\mspace{14mu} C_{{cap},p}} \right\rbrack{\quad\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}}}$ where each element of the array C_(cap) includes a capital cost value C_(cap,k) for a particular capital purchase k=1 . . . p and each element of the matrix B_(cap) includes a binary decision variable for a particular capital purchase k=1 . . . p at a particular time step i=1 . . . h of the optimization period.

Still referring to FIG. 10, process 1000 is shown to include optimizing an objective function including the costs Cost_(op), Cost_(main), and Cost_(cap) to determine an optimal maintenance strategy for the building equipment (step 1016). Step 1016 can include generating the objective function J by summing the operational cost term, the maintenance cost term, and the capital cost term formulated in steps 1010-1014. One example of an objective function which can be generated in step 1016 is shown in the following equation:

$J = {{\sum\limits_{i = 1}^{h}{C_{{op},i}P_{{op},i}\Delta\; t}} + {\sum\limits_{i = 1}^{h}{C_{{main},i}B_{{main},i}}} + {\sum\limits_{i = 1}^{h}{C_{{cap},i}P_{{cap},i}}}}$ where C_(op,i) is the cost per unit of energy (e.g., $/kWh) consumed by connected equipment 610 at time step i of the optimization period, P_(op,i) is the power consumption (e.g., kW) of connected equipment 610 at time step i, Δt is the duration of each time step i, C_(main,i) is the cost of maintenance performed on connected equipment 610 at time step i, B_(main,i) is a binary variable that indicates whether the maintenance is performed, C_(cap,i) is the capital cost of purchasing a new device of connected equipment 610 at time step i, B_(cap,i) is a binary variable that indicates whether the new device is purchased, and h is the duration of the horizon or optimization period over which the optimization is performed.

Another example of an objective function which can be generated in step 1016 is shown in the following equation:

     J = C_(op)P_(op)Δ t + C_(main)B_(main) + C_(cap)B_(cap) $J = {{{\left\lbrack {C_{{op},1}\mspace{20mu} C_{{op},2}\mspace{20mu}\ldots\mspace{14mu} C_{{op},h}} \right\rbrack\left\lbrack {P_{{op},1}\mspace{20mu} P_{{op},2}\mspace{14mu}\ldots\mspace{14mu} P_{{op},h}} \right\rbrack}^{T}\Delta\; t} + {\quad{\left\lbrack {C_{{main},1}\mspace{20mu} C_{{main},2}\mspace{20mu}\ldots\mspace{14mu} C_{{main},m}} \right\rbrack{\quad{\begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix} + {\quad{\left\lbrack {C_{{cap},1}\mspace{20mu} C_{{cap},2}\mspace{14mu}\ldots\mspace{14mu} C_{{cap},p}} \right\rbrack\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}}}}}}}}$ where the array C_(op) includes an energy cost value C_(op,i) for a particular time step i=1 . . . h of the optimization period, the array P_(op) includes a power consumption value P_(op,i) for a particular time step i=1 . . . h of the optimization period, each element of the array C_(main) includes a maintenance cost value C_(main,j) for a particular maintenance activity j=1 . . . m, each element of the matrix B_(main) includes a binary decision variable for a particular maintenance activity j=1 . . . m at a particular time step i=1 . . . h of the optimization period, each element of the array C_(cap) includes a capital cost value C_(cap,k) for a particular capital purchase k=1 . . . p, and each element of the matrix B_(cap) includes a binary decision variable for a particular capital purchase k=1 . . . p at a particular time step i=1 . . . h of the optimization period.

Step 1016 can include imposing constraints on one or more variables or parameters in the objective function J. The constraints can include any of the equations or relationships described with reference to operational cost predictor 910, maintenance cost predictor 920, and capital cost predictor 930. For example, step 1016 can include imposing a constraint which defines the power consumption values P_(op,i) for one or more devices of the building equipment as a function of the ideal power consumption P_(ideal,i) and the efficiency η_(i) (e.g., P_(op,i)=P_(ideal,i)/η_(i)). Step 1016 can include imposing a constraint which defines the efficiency η_(i) as a function of the binary decision variables B_(main,i) and B_(cap,i), as described with reference to efficiency updater 911 and efficiency degrader 913. Step 1016 can include imposing a constraint which constrains the binary decision variables B_(main,i) and B_(cap,i) to a value of either zero or one and defines the binary decision variables B_(main,i) and B_(cap,i) as a function of the reliability Reliability_(i) of connected equipment 610, as described with reference to maintenance estimator 922 and purchase estimator 932. Step 1016 can include imposing a constraint which defines the reliability Reliability_(i) of connected equipment 610 as a function of the equipment performance information (e.g., operating conditions, run hours, etc.) as described with reference to reliability estimators 924 and 934.

Step 1016 can include optimizing the objective function J to determine the optimal values of the binary decision variables B_(main,i) and B_(cap,i) over the duration of the optimization period. Step 1016 can include using any of a variety of optimization techniques to formulate and optimize the objective function J. For example, step 1016 can include using integer programming, mixed integer linear programming, stochastic optimization, convex programming, dynamic programming, or any other optimization technique to formulate the objective function J, define the constraints, and perform the optimization. These and other optimization techniques are known in the art and will not be described in detail here.

In some embodiments, step 1016 includes using mixed integer stochastic optimization to optimize the objective function J. In mixed integer stochastic optimization, some of the variables in the objective function J can be defined as functions of random variables or probabilistic variables. For example, the decision variables B_(main,i) and B_(cap,i) can be defined as binary variables that have probabilistic values based on the reliability of the building equipment. Low reliability values can increase the probability that the binary decision variables B_(main,i) and B_(cap,i) will have a value of one (e.g., B_(main,i)=1 and B_(cap,i)=1), whereas high reliability values can increase the probability that the binary decision variables B_(main,i) and B_(cap,i) will have a value of zero (e.g., B_(main,i)=0 and B_(cap,i)=0). In some embodiments, step 1016 includes using a mixed integer stochastic technique to define the values of the binary decision variables B_(main,i) and B_(cap,i) as a probabilistic function of the reliability of the building equipment.

As discussed above, the objective function J can represent the predicted cost of operating, maintaining, and purchasing one or more devices of the building equipment over the duration of the optimization period. In some embodiments, step 1016 includes projecting these costs back to a particular point in time (e.g., the current time) to determine the net present value (NPV) of the one or more devices of the building equipment at a particular point in time. For example, step 1016 can include projecting each of the costs in objective function J back to the current time using the following equation:

${NPV}_{cost} = {\sum\limits_{i = 1}^{h}\frac{{Cost}_{i}}{\left( {1 + r} \right)^{i}}}$ where r is the interest rate, Cost_(i) is the cost incurred during time step i of the optimization period, and NPV_(cost) is the net present value (i.e., the present cost) of the total costs incurred over the duration of the optimization period. In some embodiments, step 1016 includes optimizing the net present value NPV_(cost) to determine the NPV of the building equipment at a particular point in time.

As discussed above, one or more variables or parameters in the objective function J can be updated dynamically based on closed-loop feedback from the building equipment. For example, the equipment performance information received from the building equipment can be used to update the reliability and/or the efficiency of the building equipment. Step 1016 can include optimizing the objective function J periodically (e.g., once per day, once per week, once per month, etc.) to dynamically update the predicted cost and/or the net present value NPV_(cost) based on the closed-loop feedback from the building equipment.

In some embodiments, step 1016 include generating optimization results. The optimization results can include the optimal values of the decision variables in the objective function J for each time step i in the optimization period. The optimization results include operating decisions, equipment maintenance decisions, and/or equipment purchase decisions for each device of the building equipment. In some embodiments, the optimization results optimize the economic value of operating, maintaining, and purchasing the building equipment over the duration of the optimization period. In some embodiments, the optimization results optimize the net present value of one or more devices of the building equipment at a particular point in time. The optimization results can cause BMS 606 to activate, deactivate, or adjust a setpoint for the building equipment in order to achieve the optimal values of the decision variables specified in the optimization results.

In some embodiments, process 1000 includes using the optimization results to generate equipment purchase and maintenance recommendations. The equipment purchase and maintenance recommendations can be based on the optimal values for the binary decision variables B_(main,i) and B_(cap,i) determined by optimizing the objective function J. For example, a value of B_(main,25)=1 for a particular device of the building equipment can indicate that maintenance should be performed on that device at the 25^(th) time step of the optimization period, whereas a value of B_(main,25)=0 can indicate that the maintenance should not be performed at that time step. Similarly, a value of B_(cap,25)=1 can indicate that a new device of the building equipment should be purchased at the 25^(th) time step of the optimization period, whereas a value of B_(cap,25)=0 can indicate that the new device should not be purchased at that time step.

In some embodiments, the equipment purchase and maintenance recommendations are provided to building 10 (e.g., to BMS 606) and/or to client devices 448. An operator or building owner can use the equipment purchase and maintenance recommendations to assess the costs and benefits of performing maintenance and purchasing new devices. In some embodiments, the equipment purchase and maintenance recommendations are provided to service technicians 620. Service technicians 620 can use the equipment purchase and maintenance recommendations to determine when customers should be contacted to perform service or replace equipment.

Still referring to FIG. 10, process 1000 is shown to include updating the efficiency and the reliability of the building equipment based on the optimal maintenance strategy (step 1018). In some embodiments, step 1018 includes updating the efficiency η_(i) for one or more time steps during the optimization period to account for increases in the efficiency η of the building equipment that will result from performing maintenance on the building equipment or purchasing new equipment to replace or supplement one or more devices of the building equipment. The time steps i at which the efficiency η_(i) is updated can correspond to the predicted time steps at which the maintenance will be performed or the equipment will replaced. The predicted time steps at which maintenance will be performed on the building equipment can be defined by the values of the binary decision variables B_(main,i) in the objective function J. Similarly, the predicted time steps at which the building equipment will be replaced can be defined by the values of the binary decision variables B_(cap,i) in the objective function J.

Step 1018 can include resetting the efficiency η_(i) for a given time step i if the binary decision variables B_(main,i) and B_(cap,i) indicate that maintenance will be performed at that time step and/or new equipment will be purchased at that time step (i.e., B_(main,i)=1 and/or B_(cap,i)=1). For example, if B_(main,i)=1, step 1018 can include resetting the value of η_(i) to η_(main), where η_(main) is the efficiency value that is expected to result from the maintenance performed at time step i. Similarly, if B_(cap,i)=1, step 1018 can include resetting the value of η_(i) to η_(cap), where η_(cap) is the efficiency value that is expected to result from purchasing a new device to supplement or replace one or more devices of the building equipment performed at time step i. Step 1018 can include resetting the efficiency η_(i) for one or more time steps while the optimization is being performed (e.g., with each iteration of the optimization) based on the values of binary decision variables B_(main,i) and B_(cap,i).

Step 1018 can include determining the amount of time Δt_(main,i) that has elapsed since maintenance was last performed on the building equipment based on the values of the binary decision variables B_(main,i). For each time step i, step 1018 can examine the corresponding values of B_(main) at time step i and each previous time step (e.g., time steps i−1, i− 2, . . . , 1). Step 1018 can include calculating the value of Δt_(main,i) by subtracting the time at which maintenance was last performed (i.e., the most recent time at which B_(main,i)=1) from the time associated with time step i. A long amount of time Δt_(main,i) since maintenance was last performed can result in a lower reliability, whereas a short amount of time since maintenance was last performed can result in a higher reliability.

Similarly, step 1018 can include determining the amount of time Δt_(cap,i) that has elapsed since the building equipment were purchased or installed based on the values of the binary decision variables B_(cap,i). For each time step i, step 1018 can examine the corresponding values of B_(cap) at time step i and each previous time step (e.g., time steps i−1, i−2, . . . , 1). Step 1018 can include calculating the value of Δt_(cap,i) by subtracting the time at which the building equipment were purchased or installed (i.e., the most recent time at which B_(cap,i)=1) from the time associated with time step i. A long amount of time Δt_(cap,i) since the building equipment were purchased or installed can result in a lower reliability, whereas a short amount of time since the building equipment were purchased or installed can result in a higher reliability

Some maintenance activities can be more expensive than other. However, different types of maintenance activities can result in different levels of improvement to the efficiency η and/or the reliability of the building equipment. For example, merely changing the oil in a chiller can result in a minor improvement in efficiency η and/or a minor improvement in reliability, whereas completely disassembling the chiller and cleaning all of the chilled water tubes can result in a significantly greater improvement to the efficiency η and/or the reliability of the building equipment. Accordingly, multiple different levels of post-maintenance efficiency (i.e., η_(main)) and post-maintenance reliability (i.e., Reliability_(main)) can exist. Each level of η_(main) and Reliability_(main) can correspond to a different type of maintenance activity.

In some embodiments, step 1018 includes identifying the maintenance activity associated with each binary decision variable B_(main,j,i) and resets the efficiency η to the corresponding post-maintenance efficiency level η_(main,j) if B_(main,j,i)=1. Similarly, step 1018 can include identifying the maintenance activity associated with each binary decision variable B_(main,j,i) and can reset the reliability to the corresponding post-maintenance reliability level Reliability_(main,j) if B_(main,j,i)=1.

Some capital purchases can be more expensive than other. However, different types of capital purchases can result in different levels of improvement to the efficiency η and/or the reliability of the building equipment. For example, purchasing a new sensor to replace an existing sensor can result in a minor improvement in efficiency η and/or a minor improvement in reliability, whereas purchasing a new chiller and control system can result in a significantly greater improvement to the efficiency η and/or the reliability of the building equipment. Accordingly, multiple different levels of post-purchase efficiency (i.e., η_(cap)) and post-purchase reliability (i.e., Reliability_(cap)) can exist. Each level of η_(cap) and Reliability_(cap) can correspond to a different type of capital purchase.

In some embodiments, step 1018 includes identifying the capital purchase associated with each binary decision variable B_(main,k,i) and resetting the efficiency η to the corresponding post-purchase efficiency level η_(cap,k) if B_(cap,k,i)=1. Similarly, step 1018 can include identifying the capital purchase associated with each binary decision variable B_(cap,k,i) and can resetting the reliability to the corresponding post-purchase reliability level Reliability_(cap,k) if B_(main,k,i)=1.

Degradation of Building Equipment Over Time

Overview

Referring generally to FIGS. 11-13, graphs 1100-1300 illustrating degradation of building equipment over time are shown, according to some embodiments. Building equipment generally degrades over time. As building equipment degrades, operational costs associated with running the equipment may increase since the building equipment requires more frequent maintenance to maintain an acceptable efficiency, consumes more power, etc. In some embodiments, performing maintenance and/or replacing the building equipment reduces the degradation of the building equipment, thereby reducing operational costs. In some embodiments, replacement includes replacement of building equipment altogether and/or replacement of components in the building equipment. In some embodiments, objective function optimizer 940 described with reference to FIG. 9 is configured to determine when building equipment should undergo maintenance and/or replacement. Performing maintenance and/or replacing building equipment may incur maintenance costs and/or capital costs, but may result in a reduction of operational costs. In some embodiments, if maintenance and/or replacement is performed, the benefits from the reduced operational costs outweigh the costs associated with maintenance and/or replacement. For example, entirely replacing an indoor variable refrigerant flow (VRF) unit that is consuming a large amount of power may incur additional capital costs, but may significantly reduce operational costs as the replaced unit may not require as much power to operate.

Average Power Consumption and Degradation

Referring now to FIG. 11, a graph 1100 illustrating degradation and average power consumption of building equipment over time is shown, according to some embodiments. Graph 1100 illustrates degradation and average power consumption of building equipment over a time period 1106. In some embodiments, time period 1106 is or includes an optimization period. In some embodiments, time period 1106 includes multiple optimization periods. Time period 1106 begins at time step t₀ and ends at a time step t₄₀, according to some embodiments. As shown in graph 1100, degradation of building equipment is related to average power consumption of the building equipment. In general, as the degradation of the building equipment increases, so does the average power consumption of the building equipment. This may be due to decreased efficiency of the building equipment as the degradation of the equipment increases. In some embodiments, model predictive maintenance (MPM) system 602 is configured to reduce the degradation of the building equipment by determining when to perform maintenance and/or replace the building equipment as determined through optimization (e.g., minimization) of the objective function J. In some embodiments, while optimizing the objective function J, MPM system 602 determines optimal values of decision variables such that total combined costs are minimized. In some embodiments, the total combined costs are minimized by reducing operational costs (due to performing maintenance and/or replacement) without incurring excessive maintenance costs and/or capital costs.

It should be understood that optimizing the objective function J refers to a result of performing an optimization process. Optimizing the objective function J may not indicate that an optimal solution to the objective function J can/will be determined. Optimization of the objective function J can be performed whether or not a true optimal result is obtained.

Graph 1100 is shown to include series 1102 and series 1104. In some embodiments, series 1102 illustrates an increase in degradation and average power consumption of building equipment over time (e.g., over time period 1106) if the building equipment does not receive any equipment servicing (i.e., no maintenance and no replacement). As shown in graph 1100, the rate of increase of degradation of the building equipment may increase over time (as illustrated by series 1102) if no equipment services are performed. Series 1102 may follow an exponential trend, a linear trend, a logarithmic trend, etc., or any other trend that represents degradation and average power consumption of the building equipment over time if equipment services are not performed, according to various embodiments. In some embodiments, series 1102 illustrates a worst-case situation where operational costs increase without any attempt to reduce the operational costs through maintenance and/or replacement.

In some embodiments, series 1104 illustrates degradation and average power consumption of building equipment over time, if the building equipment is provided one or more equipment services. Series 1104 represents building equipment undergoing equipment servicing at time steps t₁₀, t₂₀, t₃₀, and t₄₀, according to some embodiments. Each equipment servicing can reduce the degradation and average power consumption of the building equipment to a degradation value 1114. In some embodiments, equipment servicing occurs at a routine schedule for series 1104 (e.g., every 10 days, every 10 weeks, etc.). In some embodiments, equipment servicing occurs due to the building equipment exceeding a maximum allowable degradation value such that costs are no longer near an optimal (e.g., minimal) level. For example, a need for equipment servicing can be determined for the building equipment after a current degradation value is twice degradation value 1114. Regular equipment servicing may keep operational costs low by not allowing the building equipment to reach a high degradation value and thereby maintain a desired level of efficiency of the building equipment. Avoiding the high degradation value can ensure that the building equipment does not draw excessive amounts of power while operating. In some embodiments, objective function optimizer 940 determines optimal values of decision variables to optimize (i.e., minimize) total combined costs associated with operational costs, maintenance costs, and capital costs. In some embodiments, the decision variables indicate when equipment servicing (e.g., maintenance and/or replacement) should occur to achieve the optimal (e.g., minimized) total combined costs.

Series 1104 and series 1102 are shown to begin at degradation value 1114 at time t₀. Likewise, series 1104 is shown to substantially return to degradation value 1114 after each equipment servicing. In some embodiments, degradation value 1114 is a minimum achievable value of degradation for the equipment. In some embodiments, degradation value 1114 is some value greater than zero. In some embodiments, degradation value 1114 is substantially equal to zero (e.g., for a highly efficient device or a device operating at isentropic efficiency). In some embodiments, each consecutively occurring equipment servicing in series 1104 returns the degradation value of the building equipment near degradation value 1114, with diminishing returns. For example, as consecutive equipment services are performed, the benefits from performing the equipment services may decrease. Instead, each equipment servicing in series 1104 may return the degradation value of the building equipment to a new reduced degradation value such that the new reduced degradation value is a higher degradation value than a previous reduced degradation value (even if negligibly so). In some embodiments, the new reduced degradation value increases with each successive equipment servicing as some components of the building equipment may continue to age despite the equipment servicing. Δt some point, the building equipment may need to be replaced to entirely return the degradation to degradation value 1114.

Graph 1100 is also shown to include an average power consumption difference 1112. In some embodiments, average power consumption difference 1112 illustrates a difference between a first average power consumption value 1108 shown as P₁ and a second average power consumption value 1110 shown as P₂. In some embodiments, P₁ is an overall average power consumption of second series 1104. In some embodiments, P₂ is an overall average power consumption of series 1102. Average power consumption difference 1112 can be represented as the difference between P₂ and P₁ (i.e., P₂-P₁). Average power consumption difference 1112 represents reduced power consumption for the case when equipment servicing is performed intermittently (series 1104) as compared to the case when equipment servicing is not performed (series 1102), according to some embodiments. By performing equipment servicing intermittently, an average amount of power drawn over time period 1106 can be significantly reduced (i.e., average power consumption difference 1112 increases), resulting in a reduction in operational costs.

Failure Rate of Building Equipment Over Time

Referring now to FIG. 12, graph 1200 illustrates failure rate of building equipment over time. Graph 1200 is shown to include a curve 1202 illustrating failure rate of building equipment over time. Curve 1202 includes three sections: a pre-useful life section 1206, a useful life section 1204, and a post-useful life section 1208, according to some embodiments. In some embodiments, curve 1202 is used to determine how long performing equipment servicing on the building equipment will extend the building equipment's useful life.

Pre-useful life section 1206 of curve 1202 illustrates failure rate of the building equipment before useful life section 1204 begins. Pre-useful life section 1206 is shown to begin at a high failure rate which falls to a lower failure rate at the end of pre-useful life section 1206. In some embodiments, pre-useful life section 1206 begins at the high failure rate if the building equipment is experiencing many failures after being installed in a building. For example, a newly installed outdoor VRF unit in a VRF system may initially be defective, and as such the outdoor VRF unit may have a high failure rate until it is fixed or replaced. As another example, the newly installed outdoor VRF unit may be connected improperly and short circuited in pre-useful life section 1206. In some embodiments, building equipment will have a low failure rate upon installation (e.g., the building equipment is working as expected). When building equipment begins with a low failure rate in pre-useful life section 1206, pre-useful life section 1206 may be short. When building equipment begins with a low failure rate, useful life section 1204 of curve 1202 may begin immediately, thereby skipping pre-useful life section 1206 altogether.

In some embodiments, useful life section 1204 is an amount of time where the building equipment is operating with an acceptable failure rate. A time progress, the failure rate of the building equipment may increase. As the failure rate of the building equipment increases, total costs associated with operating and maintaining the building equipment may increase as well. However, performing equipment servicing can extend the useful life section 1204 of the building equipment by reducing an amount of failures of the building equipment. In some embodiments, as more equipment servicing is performed, useful life section 1204 is increased. In general, extending useful life section 1204 results in increased maintenance costs and/or capital costs as maintenance will be required to be performed on the building equipment to keep the failure rate low, and/or components of the building equipment may need to be purchased and replaced. Eventually, performing equipment servicing (e.g., maintenance and building equipment component replacement) to extend useful life section 1204 may be a sub-optimal (with respect to costs) solution due to increased maintenance costs and/or capital costs. For example, at some point, the benefits of extending useful life section 1204 may be outweighed by the costs associated with extending useful life section 1204 (by performing maintenance and/or component replacement). In some embodiments, due to general equipment wear, the failure rate of the building equipment will increase and curve 1202 will transition into post-useful life section 1208.

In some embodiments, post-useful life section 1208 indicates a span of time where the building equipment has passed useful life section 1204, but has not yet been replaced. In some embodiments, in post-useful life section 1208, the building equipment experiences increased failure rate since the building equipment deteriorates. In some embodiments, the building equipment deteriorates due to general equipment wear. In some embodiments, the building equipment deteriorates if general equipment servicing is not performed at the same amount as useful life section 1204 and/or is not performed at all due to increased costs. In general, general equipment servicing may only extend a useful life of the building equipment to a certain point at which it can become more cost effective to replace the unit entirely. In some embodiments, as soon as post-useful life section 1208 begins, full replacement of the building equipment should be scheduled, such that the building equipment is replaced entirely. In this way, post-useful life section 1208 can be shortened and increased operational costs associated with a high failure rate can be minimized. In some embodiments, after the building equipment is fully replaced, post-useful life section 1208 ends.

Efficiency Degradation of Building Equipment Over Time

Referring now to FIG. 13, graph 1300 illustrates functional performance (e.g., efficiency) of building equipment over time, according to some embodiments. Graph 1300 is shown to include a series 1302 and a series 1304. In some embodiments, series 1302 illustrates the case when equipment servicing (e.g., maintenance and/or part/component replacement) is performed in response to the building equipment reaching a minimum efficiency threshold 1310. In some embodiments, series 1304 represents a proactive approach to maintenance such that multiple equipment services are performed before the building equipment reaches minimum efficiency threshold 1310.

In some embodiments, series 1302 illustrates how performing equipment servicing in response to reaching minimum efficiency threshold 1310 leads to a quicker decline in efficiency as compared to the case when equipment servicing is performed intermittently (series 1304). An efficiency value of series 1302 can be determined based on equipment information gathered from the building equipment (e.g., a value of a performance variable) and a model of the equipment (e.g., a degradation model, an ideal value of a performance variable, etc.). In some embodiments, the efficiency value of equipment is determined based on operational costs (e.g., production per unit cost). For example, a higher operational cost can indicate a lower efficiency value of the building equipment.

A first equipment servicing point 1306 is shown as a possible equipment servicing during series 1302. In some embodiments, first equipment servicing point 1306 occurs in response to the efficiency value (i.e., the Y-axis value) of series 1302 reaching minimum efficiency threshold 1310 at time t₁. In some embodiments, minimum efficiency threshold 1310 is an efficiency value of building equipment that MPM system 602 attempts to avoid as to not incur very high operational costs. First equipment servicing point 1306 can briefly prolong an amount of time the building equipment is deemed usable; however, without routine equipment servicing, the additional amount of time the building equipment is deemed usable may be short. In some embodiments, equipment servicing occurs for series 1302 every time the efficiency value of the building equipment is equal to or below minimum efficiency threshold 1310. Each subsequent equipment servicing may have less of an effect on the efficiency value of the building equipment as the building equipment overall continues to degrade. Eventually, an amount spent on equipment servicing can be determined to be too large by MPM system 602, and the building equipment can be scheduled to be replaced.

Graph 1300 is also shown to include series 1304 illustrating efficiency of building equipment over time provided routine equipment servicing. Routine equipment servicing can prolong an amount of usable time of the building equipment. Series 1304 is shown to include many small equipment services 1312. Small equipment services 1312 can include, for example, routine inspections, some part replacement, fluid (e.g., coolant) changes, etc. In some embodiments, each small equipment service 1312 slightly prolongs the usable time of the building equipment. While each small equipment service 1312 only extends the usable time of the building equipment slightly, by repeatedly performing small equipment services 1312, the usable time of the building equipment can be significantly increased. Series 1304 is also shown to include a major equipment servicing 1308. Major equipment servicing 1308 can significantly increase the usable time of the building equipment. Major equipment servicing 1308 may include, for example, numerous part replacements of the building equipment, a software upgrade, a number of small equipment services 1312, refurbishing, etc.

Equipment services in series 1304 are shown to occur before the efficiency value of the building equipment reaches minimum efficiency threshold 1310. Series 1304 is shown to reach minimum efficiency threshold 1310 at a time t₂. In some embodiments, the difference between t₂ and t₁ indicates an additional period of time before the building equipment reaches minimum efficiency threshold 1310 based on different equipment servicing methods. In some embodiments, t₂ is greater than t₁ due to intermittent equipment servicing. By preemptively performing the equipment services, the usable time of the building equipment can be significantly increased before the building equipment has to be entirely replaced.

Model Predictive Maintenance System with Incentive Incorporation

Overview

Referring generally to FIGS. 14-17, systems and methods for a model predictive maintenance system with incentive incorporation are shown, according to some embodiments. In some embodiments, any of the systems and method described in greater detail below with reference to FIGS. 14-17 are incorporated in MPM system 602 described in greater detail above with reference to FIGS. 6-10. For example, high level optimizer 832 of model predictive maintenance system 602 described in greater detail above with reference to FIGS. 8-9 may include any or all of the systems and methods (e.g., cost incentives) described herein below. In some embodiments, MPM system 602 is configured to receive one or more cost incentives to further optimize the objective function J. A cost incentive may describe any incentive available for use in MPM that can effectively reduce a cost. Specifically, a cost incentive can reduce a cost of, for example, performing maintenance, replacing building equipment, upgrading a system, etc. For example, a cost incentive may be a tax incentive that encourages replacing one or more refrigerants in a variable refrigerant flow (VRF) system to receive a tax benefit at the end of a fiscal year. As another example, a cost incentive may be associated with a green building incentive, such that a cost of replacing building equipment parts with environmentally friendly alternatives is reduced. In some embodiments, the one or more cost incentives are added as a negative cost term (i.e., a revenue term) to the objective function J to reduce overall costs. In some embodiments, a cost incentive results in an increase in operational costs, maintenance costs, and/or capital costs depending on the cost incentive offered. However, savings from the cost incentive may outweigh additional costs incurred, and can still be determined to further optimize the objective function J. For example, replacing refrigerant in a VRF system may incur additional capital costs and/or maintenance costs, but a cost incentive for replacing the refrigerant can be a larger amount than the additional capital costs and/or maintenance costs, thereby further optimizing the objective function J.

In some embodiments, a cost incentive considered during optimization of the objective function J is available at a current time and/or will be available at some future time. In some embodiments, if a cost incentive is currently available, benefits of the cost incentive are able to be obtained immediately and/or before the cost incentive expires. If a cost incentive is available at a future time, the cost incentive can be scheduled to be obtained at some future time when the cost incentive is available. As such, if optimizing the objective function J, the optimization may consider both available cost incentives and future cost incentives to achieve a lowest cost over an optimization period. It should be understood that an available cost incentive can refer to cost incentives currently available and to cost incentives that will be available at a future time.

Model Predictive Maintenance with Cost Incentives

Referring now to FIG. 14, a graph 1400 illustrating cumulative maintenance expenditures over time with a cost incentive is shown, according to some embodiments. In some embodiments, graph 1400 is shown to account for cost incentives relating to maintenance (i.e., the maintenance term of the objective function J) of building 10. Similarly, graph 1400 can be used in a similar fashion to model cost incentives relating to capital purchases (i.e., the capital cost term of the objective function J). In some embodiments, a cost incentive is implemented by a government (e.g., a federal government, a state government, a municipal government, etc.) to incentivize upgrades or replacement of building equipment (or a component of the building equipment) through tax savings. In some embodiments, a cost incentive may be implemented by an independent organization, group, individual, etc. For example, a private company may want to sell a large amount of a product and other a cost incentive for buying a particular quantity of the product.

Graph 1400 may illustrate how maintenance expenditures are determined over optimization period 1404 by high level optimizer 832 described below with reference to FIG. 15. In some embodiments, graph 1400 includes an optimization period 1404 starting at a time step i=1 through a final time step h. In some embodiments, graph 1400 includes a first maintenance expenditure 1406, a second maintenance expenditure 1408, and a third maintenance expenditure 1410. In general, a maintenance expenditure can be shown to occur at time step i as B_(main,i)=1. In general, a maintenance expenditure can be shown not to occur at time step i as B_(main,i)=0.

First maintenance expenditure 1406 is shown to occur at a time step i=6 as B_(main,6)=1. In some embodiments, first maintenance expenditure 1406 occurs due to a determination from high level optimizer 832 described below with reference to FIG. 15 that maintenance should occur at time step i=6. First maintenance expenditure 1406 can be described as Cost_(main,1). After first maintenance expenditure 1406 is performed, a cumulative maintenance expenditure Cost_(main) can be described as Cost_(main)=Cost_(main,1). Δt time step i=16, second maintenance expenditure 1408 is shown to be performed, such that a cost of second maintenance expenditure 1408 can be represented as Cost_(main,2.) Similar to first maintenance expenditure 1406, second maintenance expenditure 1408 is shown to occur at time step i=16 as B_(main,16)=1. In some embodiments, second maintenance expenditure 1408 increases the cumulative maintenance expenditure Cost_(main) to Cost_(main)=Cost_(main,1)+Cost_(main,2). Further, at time step i=21, third maintenance expenditure 1410 is shown to occur, such that a cost of third maintenance expenditure 1410 can be represented as Cost_(main,3). Similar to first maintenance expenditure 1406, third maintenance expenditure 1410 is shown to occur at time step i=21 as B_(main,21)=1, according to some embodiments. In some embodiments, third maintenance expenditure 1410 increases the cumulative maintenance expenditure Cost_(main) to Cost_(main)=Cost_(main,1)+Cost_(main,2)+Cost_(main,3). Finally, Cost_(main)=Cost_(main,1)+Cost_(main,2)+Cost_(main,3) can be represented as unadjusted total maintenance expenditure 1416.

A maintenance expenditure series 1402 is shown over optimization period 1404. In some embodiments, maintenance expenditure series 1402 illustrates a cumulative maintenance expenditure at any time step i during optimization period 1404. In some embodiments, a value of maintenance expenditure series 1402 at time step h is a final cumulative maintenance expenditure during optimization period 1404.

In some embodiments, objective function optimizer 940 determines an optimal maintenance schedule over optimization period 1404. Objective function optimizer 940 can account for one or more cost incentives if determining the optimal maintenance schedule over optimization period 1404. In some embodiments, the one or more cost incentives include one or more cost incentives available at a current time and/or one or more cost incentives available at a future time. In some embodiments, a cost incentive further optimizes the objective function J by reducing cumulative costs (e.g., operational costs, maintenance costs, capital costs, etc.) over optimization period 1404. In some embodiments, additional maintenance expenditures are optimal in order to fulfill one or more requirements for a cost incentive. For example, third maintenance expenditure 1410 may have been decided to be performed by objective function optimizer 940 to fulfill requirements for a cost incentive. By implementing third maintenance expenditure 1410 into the optimal maintenance schedule over optimization period 1404, a cost incentive can be met to minimize cumulative maintenance expenditures over optimization period 1404.

Graph 1400 is also shown to include a cost benefit 1414. In some embodiments, cost benefit 1414 is an amount (e.g., $) that is deducted from unadjusted total maintenance expenditure 1416 after requirements for a cost incentive have been completed. Savings due to cost benefit 1414 may not be immediately available. For example, cost benefit 1414 may be accounted for when taxes are filed if cost benefit 1414 is a tax incentive. If cost benefit 1414 is not immediately available, MPM system 602 may make one or more decisions to incur additional costs at an earlier time step in optimization period 1404 if MPM system 602 can expect cost benefit 1414 to be accounted for at a later time step in optimization period 1404. As another example, cost benefit 1414 may not be immediately available if one or more cost incentives are future cost incentives. If any cost incentives are future cost incentives, some and/or all of cost benefit 1414 may be available at a future time if the future cost incentives are obtained. In some embodiments, cost benefit 1414 is immediately available upon fulfillment of requirements for the cost incentive. If cost benefit 1414 is immediately available, MPM system 602 may make determinations regarding when to fulfill the requirements to optimize the objective function J.

A cost savings 1412 is shown as cost benefit 1414 minus third maintenance expenditure 1410. In some embodiments, cost savings 1412 is used by objective function optimizer 940 when determining optimal values of decision variables in the objective function. Objective function optimizer 940 may use cost savings 1412 as a “cost” of performing third maintenance activity 1410 when performing an optimization. In graph 1400, cost savings 1412 is a negative amount indicating cost is reduced by performing third maintenance activity 1410. If cost savings 1412 is not a large enough amount as determined by objective function optimizer 940, one or more maintenance expenditures during optimization period 1404 may not be performed. If cost savings 1412 is not a large enough value, objective function optimizer 940 may determine the optimal maintenance schedule to not include cost benefit 1414 and/or maintenance activities to fulfill cost incentive requirements to obtain cost benefit 1414.

Referring now to FIG. 15, a block diagram illustrating MPM system 602 in greater detail is shown, according to some embodiments. A cost incentive service 838 is shown to provide one or more cost incentives to high level optimizer 832. Cost incentive service 838 can be, for example, an external website, a cost incentive monitoring service of BMS 606, a database storing cost incentive information, a person providing cost incentive information to MPM system 602, etc. In some embodiments, cost incentive service 838 will provide every cost incentive available when communicating with MPM system 602. In some embodiments, cost incentive service 838 may select and provide one or more specific cost incentives that building 10 may be able to utilize and may also decide not to provide some cost incentives. For example, cost incentive service 838 may determine that a cost incentive is not applicable to building 10 and may decide to not provide said cost incentive to MPM system 602. As another example, cost incentive service 838 may determine that a tax incentive for replacing refrigerant in a VRF system is applicable to building 10 and may decide to provide said tax incentive to MPM system 602. In some embodiments, by reducing how many cost incentives are provided to MPM system 602 for consideration, cost incentive service 838 helps increase processing efficiency in MPM system 602 as less variables need to be accounted for when determining optimal values of decision variables in the objective function J. In some embodiments, cost incentives selected and provided by cost incentive service 838 are used to reduce operational costs, maintenance costs, and/or capital costs. In some embodiments, high level optimizer 832 uses cost incentives provided by cost incentive service 838 to optimize (i.e., minimize) the objective function J by reducing total cost over an optimization period. High level optimizer 832 utilizing cost incentives is described in greater detail below with reference to FIG. 16.

In some embodiments, cost incentive service 838 does not provide any cost incentives if no cost incentives are available. If no cost incentives are available, MPM may be performed without accounting for any cost incentives.

Referring now to FIG. 16, high level optimizer 832 described with reference to FIGS. 9 and 15 is shown in greater detail, according to some embodiments. High level optimizer 832 is shown to include a cost incentive manager 950. In some embodiments, cost incentive manager 950 is configured to receive one or more cost incentive (e.g., from cost incentive service 838 described with reference to FIG. 15). In some embodiments, cost incentive manager 950 does not receive any cost incentives, in which case high level optimizer 832 generates and optimizes an objective function without accounting for any cost incentives.

In some embodiments, cost incentive manager 950 is configured to receive cost incentives provided by cost incentive service 838 described with reference to FIG. 15. In some embodiments, based on the provided cost incentives, cost incentive manager 950 is configured to determine if a cost incentive is applicable to maintenance costs and/or capital costs. For example, a cost incentive can indicate a tax savings is available if a new VRF system is purchased. However, if no cost incentives are available, cost incentive manager 950 may not perform other significant operations. If no cost incentives are available, model predictive maintenance may be performed without any cost incentive information. Based on the cost incentive, cost incentive manager 950 may determine that information regarding the cost incentive should be provided to capital cost predictor 930 as one or more capital cost incentives. As another example, a cost incentive provided to cost incentive manager 950 may indicate a cost savings is (or will be) available if maintenance is performed on a heating, ventilation, and air conditioning (HVAC) system. Based on the cost incentive, cost incentive manager 950 may determine that one or more maintenance cost incentives describing the cost incentive should be provided to maintenance cost predictor 920.

In some embodiments, the cost incentive define a time period when the cost incentive is available. If the time period is defined, cost incentive manager 950 may indicate the time period in the one or more capital cost incentives and/or the one or more maintenance cost incentives. The time period may act as a constraint on the optimization performed by objective function optimizer 940. For example, if a tax incentive is offered by a federal government and ends in 3 months, requirements for the tax incentive may need to be met before the 3 months if the tax incentive is to be obtained. As another example, if a green building incentive is not currently available, but will be available in 2 weeks from a current time, requirements for the green building incentive may need to be met at a later time once the green building incentive is available. As such, cost incentive manager 950 may determine how long a particular cost incentive is available for to ensure that requirements of the particular cost incentive are not met on time.

Cost incentive manager 950 may determine that one or more cost incentives include information applicable to both maintenance cost predictor 920 and capital cost predictor 930. When a cost incentive includes information applicable to both maintenance cost predictor 920 and capital cost predictor 930, cost incentive manager 950 may divide information regarding the cost incentive into one or more maintenance cost incentives and/or one or more capital cost incentive to be provided to maintenance cost predictor 920 and capital cost predictor 930 respectively. In some embodiments, by dividing information regarding a cost incentive into one or more maintenance cost incentives and/or one or more capital cost incentives, only information pertinent to maintenance cost predictor 920 and capital cost predictor 930 will be provided to each. For example, consider a cost incentive providing a tax savings when a building both purchases a new VRF system and replaces old refrigerant in the building, according to some embodiments. Based on the cost incentive, cost incentive manager 950 can divide the cost incentive into a maintenance cost incentive including information regarding replacing refrigerant, and a capital cost incentive including information regarding purchase of the new VRF system. When the maintenance cost incentive and the capital cost incentive are provided to maintenance cost predictor 920 and capital cost predictor 930 respectively, only information pertinent to each cost predictor will be provided (e.g., capital cost predictor 930 will only receive information regarding purchase of the new VRF system as it does not require information regarding replacement of refrigerant), according to some embodiments.

In some embodiments, maintenance cost predictor 920 determines a maintenance cost term based on provided equipment performance information and one or more maintenance cost incentives. In some embodiments, maintenance cost predictor 920 determines the maintenance cost term by predicting a total maintenance cost savings for the one or more maintenance cost incentives provided by cost incentive manager 950. When determining the maintenance cost term of the objective function J, maintenance cost predictor 920 may need to include one or more additional variables in C_(main) and/or B_(main) to account for more possible maintenances. In some embodiments, maintenance cost incentives introduce one or more types of maintenance that would not otherwise be considered by maintenance cost predictor 920. For example, without any cost incentives, maintenance cost predictor 920 may not consider replacing refrigerant of building 10 with a specific eco-friendly refrigerant. In this case, C_(main) may have the following form: C _(main)=[C _(main,1) C _(main,2) . . . C _(main,m)] where the array C_(main) has a size of 1×m and each element of the array C_(main) includes a maintenance cost value C_(main,j) for a particular maintenance activity j=1 . . . m, according to some embodiments.

Likewise, B_(main) may have the following form if no maintenance cost incentives are considered:

$B_{main} = \begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \end{bmatrix}$ where the matrix B_(main) has a size of m×h and each element of the matrix B_(main) includes a binary decision variable for a particular maintenance activity at a particular time step of the optimization period.

However, if a maintenance cost incentive for replacing refrigerant of building 10 with the specific eco-friendly refrigerant is provided to maintenance cost predictor 920, maintenance cost predictor 920 may generate a modified maintenance cost array C_(main,mod) and a modified maintenance decision matrix B_(main,mod) to account for the maintenance cost incentive. Based on the maintenance cost incentive, C_(main,mod) can have the following form: C _(main),mod=[C _(main,1) C _(main,2) . . . C _(main,m) C _(main,m+1)] where C_(main,m+1) indicates an additional maintenance cost value for the maintenance activity j=m+1 of replacing building refrigerant with the specific eco-friendly refrigerant, according to some embodiments.

Likewise, B_(main,mod) may have the following form to account for replacement of the specific eco-friendly refrigerant:

$B_{{main},{mod}} = \begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \\ B_{{main},{m + 1},1} & B_{{main},{m + 1},2} & \ldots & B_{{main},{m + 1},h} \end{bmatrix}$ where B_(main,mod) includes an additional row B_(main,m+1,i) for maintenance activity j=m+1 for each time step i in the optimization period, according to some embodiments. When objective function optimizer 940 optimizes (i.e., minimizes) an objective function (e.g., the objective function J) generated by objective function generator 935, objective function optimizer 940 can determine optimal values of decision variables including any related to maintenance to fulfill requirements for the maintenance cost incentive. If the maintenance cost incentive is a future maintenance cost incentive available at a future time, objective function optimizer 940 may need to account for when to fulfill requirements of the maintenance cost incentive if requirements cannot be fulfilled prior to the future maintenance cost incentive taking effect. In some embodiments, no new values/rows need to be added to C_(main,mod) and/or B_(main,mod) if a maintenance activity associated with a maintenance cost incentive already exists in C_(main) and/or B_(main) (i.e., C_(main)=C_(main,mod) and B_(main)=B_(main,mod)). In some embodiments, objective function optimizer 940 takes into account any savings incurred by the one or more maintenance cost incentives.

In some embodiments, maintenance cost predictor 920 accounts for C_(main,mod) and/or B_(main,mod) when determining a cost of maintenance Cost_(main). In some embodiments, maintenance cost predictor 920 calculates a modified cost of maintenance Cost_(main,mod) when accounting for one or more cost incentives related to performing maintenance. In general, Cost_(main,mod) can be shown by the following equations:

  Cost_(main, mod) = C_(main)B_(main) ${Cost}_{{main},{mod}} = {\left\lbrack {C_{{main},1}\mspace{25mu} C_{{main},2}\mspace{20mu}\ldots\mspace{20mu} C_{{main},m}\mspace{20mu} C_{{main},{m + 1}}} \right\rbrack{\quad\begin{bmatrix} B_{{main},1,1} & B_{{main},1,2} & \ldots & B_{{main},1,h} \\ B_{{main},2,1} & B_{{main},2,2} & \ldots & B_{{main},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{main},m,1} & B_{{main},m,2} & \ldots & B_{{main},m,h} \\ B_{{main},{m + 1},1} & B_{{main},{m + 1},2} & \ldots & B_{{main},{m + 1},h} \end{bmatrix}}}$

In some embodiments, capital cost predictor 930 determines a capital cost term based on provided equipment reliability information and one or more capital cost incentives. In some embodiments, capital cost predictor 930 determines the capital cost term by predicting a total capital cost savings for the one or more capital cost incentives provided by cost incentive manager 950. When determining the capital cost term of the objective function J, capital cost predictor 930 may need to include one or more additional variables in C_(cap) and/or B_(cap) to account for more possible capital purchases indicated by the one or more capital cost incentives.

Capital cost incentives can introduce one or more capital purchases that would not otherwise be considered by capital cost predictor 930. For example, without any cost incentives, capital cost predictor 930 may not typically consider purchasing a new boiler for building 10 during a current optimization period. In this case, C_(cap) may have the following form: C _(cap)=[C _(cap,1) C _(cap,2) . . . C _(cap,p)] where the array C_(cap) has a size of 1×p and each element of the array C_(cap) includes a cost value C_(cap,k) for a particular capital purchase k=1 . . . p, according to some embodiments.

Likewise, B_(cap) may have the following form:

$B_{cap} = \begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \end{bmatrix}$ where the matrix B_(cap) has a size of p×h and each element of the matrix B_(cap) includes a binary decision variable for a particular capital purchase at a particular time step of the optimization period.

However, if a capital cost incentive for purchasing the new boiler for building 10 is provided to capital cost predictor 930, capital cost predictor 930 can calculate a modified capital cost array C_(cap,mod) and a modified binary capital purchase decision matrix B_(cap,mod) to account for the capital purchases related to the capital cost incentive. Based on the capital cost incentive, C_(cap,mod) can have the following form: C _(cap,mod)=[C _(cap,1) C _(cap,2) . . . C _(cap,p) C _(cap,p+1)] where C_(cap,p+1) is a cost value for capital purchase k=p+1 (i.e., a cost value for purchasing the new boiler for building 10).

Likewise, B_(cap,mod) may have the following form to account for purchase of the new boiler for building 10:

$B_{{cap},{mod}} = {\quad\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \\ B_{{cap},{p + 1},1} & B_{{cap},{p + 1},2} & \ldots & B_{{cap},{p + 1},h} \end{bmatrix}}$ where B_(cap,mod) includes an additional row B_(cap,p+1,i) for maintenance activity k=p+1 for each time step i in the optimization period, according to some embodiments. In some embodiments, when objective function optimizer 940 optimizes (i.e., minimizes) an objective function (e.g., the objective function J) generated by objective function generator 935, objective function optimizer 940 determines optimal values of decision variables including any related to capital purchases to fulfill requirements for the capital cost incentive. If the capital cost incentive is a future capital cost incentive available at a future time, objective function optimizer 940 may need to account for when to fulfill requirements if requirements cannot be fulfilled prior to the future capital cost incentive taking effect. In some embodiments, no new values need to be added to C_(cap,mod) and/or B_(cap,mod) if a capital purchase associated with a capital cost incentive already exists in C_(cap,mod) and/or B_(cap,mod). In some embodiments, objective function optimizer 940 simply takes into account any savings incurred by the one or more capital cost incentives.

In some embodiments, capital cost predictor 930 accounts for C_(cap,mod) and/or B_(cap,mod) when determining a cost of capital purchases Cost_(cap). In some embodiments, capital cost predictor 930 calculates a modified cost of capital purchases Cost_(cap,mod) when accounting for one or more cost incentives related to capital purchases. In general, Cost_(cap,mod) can be shown by the following equations:

  Cost_(cap, mod) = C_(cap, mod)B_(cap, mod) ${Cost}_{{cap},{mod}} = {\left\lbrack {C_{{cap},1}\mspace{25mu} C_{{cap},2}\mspace{20mu}\ldots\mspace{20mu} C_{{cap},p}\mspace{20mu} C_{{cap},{p + 1}}} \right\rbrack{\quad\begin{bmatrix} B_{{cap},1,1} & B_{{cap},1,2} & \ldots & B_{{cap},1,h} \\ B_{{cap},2,1} & B_{{cap},2,2} & \ldots & B_{{cap},2,h} \\ \vdots & \vdots & \ddots & \vdots \\ B_{{cap},p,1} & B_{{cap},p,2} & \ldots & B_{{cap},p,h} \\ B_{{cap},{p + 1},1} & B_{{cap},{p + 1},2} & \ldots & B_{{cap},{p + 1},h} \end{bmatrix}}}$ where Cost_(cap,mod) is the modified cost of capital purchases over the optimization period.

In some embodiments, maintenance cost predictor 920 and capital cost predictor 930 feed maintenance and/or replacement information to operational cost predictor 910 so operational cost predictor 910 can update efficiency values of equipment. Based on various cost incentives, equipment may undergo maintenance and/or replacement at different time steps, thereby resulting in efficiency values of equipment being updated at different time steps than without any cost incentives.

In some embodiments, objective function generator 935 gathers each of the operational cost term, the maintenance cost term, and the capital cost term to generate the objective function J including one or more possible cost incentives to take advantage of cost savings. In some embodiments, the objective function J generated by objective function generator 935 is provided to objective function optimizer 940. Objective function optimizer 940 can determine optimal values of decision variables in the objective function J to optimize total combined cost over the optimization period. In some embodiments, objective function optimizer 940 accounts for the one or more cost incentives provided to cost incentive manager 950 when determining the optimal values of the decision variables. In some embodiments, objective function optimizer 940 determines a different set of optimal values of the decision variables that allow for building 10 to fulfill requirements for one or more cost incentives. In some embodiments, fulfilling requirements for the one or more cost incentives incurs additional maintenance costs and/or capital costs, but may reduce total combined cost if cost savings associated with the one or more cost incentives is larger than costs incurred by the additional maintenance costs and/or capital costs. In some embodiments, objective function optimizer 940 determines that additional costs incurred by maintenance costs and/or capital costs to fulfill requirements of the one or more cost incentives are greater than cost savings associated with the one or more cost incentives. If additional costs incurred by maintenance costs and/or capital costs are larger than cost savings, objective function optimizer 940 may determine maintenance and/or replacements to perform without those necessary to achieve the cost incentive.

As described above, if a cost incentive is a future cost incentive, objective function optimizer 940 may need to ensure, that requirements are not met early if the cost incentive does not allow requirements to be met early. For example, a tax incentive may be provided for replacing refrigerant and begins in 2 weeks from a current time, but does not allow for refrigerant to be replaced early and still obtain the tax incentive. If refrigerant needs to be replaced anyways within a building, objective function optimizer 940 may determine if delaying replacement to obtain the tax incentive incurs more or less cost than immediately replacing the refrigerant to lower operational costs. In some embodiments, if a cost incentive allows for requirements to be met early, objective function optimizer 940 is not required to adhere to above restrictions regarding when to fulfill requirements. However, objective function optimizer 940 may be required to account for when the cost incentive can be obtained to decide if it is worth pursuing to optimize costs.

In some embodiments, cost savings incurred for fulfilling requirements for one or more cost incentives are saved outside of a current optimization period. For example, if the current optimization period ends before taxes are filed and a cost incentive for the current optimization period includes a tax incentive, a tax savings may not be accounted for in the current optimization period. When cost savings are not accounted for in the current optimization period, optimization of the objective function J may include determining that maintenance and/or replacement activities should be performed that does not achieve the cost incentive, if that is the most cost effective solution.

In some embodiments, objective function optimizer 940 optimizes the objective function J such that cost incentives are still met to have cost savings for a future optimization period. To ensure that cost incentives are still met to have cost savings for a future optimization period, objective function optimizer 940 may account for a net present value (NPV) of future revenue so that a decision can be made during the current optimization period. For example, if cost revenue is $1,500 and will be received in 6 months, objective function optimizer 940 can use a standard NPV equation to translate the cost revenue into a value of making a decision at a current time. In general, objective function optimizer 940 may determine a net present value by the following equation:

${{NPV}\left( {i,N} \right)} = {\sum\limits_{i = 0}^{N}\frac{R_{t}}{\left( {1 + i} \right)^{t}}}$ where i is a discount rate (i.e., a return that could be earned per unit of time on an investment with similar risk), t is a time of a cost flow (e.g., a cash flow), R_(t) is a net cost (e.g., cash) flow, N is a total number of time periods, and NPV(i, N) is a net present value. Utilizing the net present value may allow the objective function optimizer 940 can pair up a decision to perform a maintenance activity with a cost revenue gained from said activity in a same optimization period. By accounting for the future optimization period, objective function optimizer 940 may be able to minimize total cost over multiple optimization periods. In some embodiments, a future cost savings setting in MPM system 602 indicates whether or not objective function optimizer 940 will consider cost savings for a future optimization period while optimizing the objective function J.

Referring now to FIG. 17, a flow diagram of a process 1700 for optimizing the objective function J given cost incentive information is shown, according to some embodiments. In some embodiments, accounting for cost incentive information when optimizing the objective function J allows for cost savings to further reduce total costs. In some embodiments, performing maintenance and/or purchasing equipment to fulfill cost incentive requirements also reduces operational costs at future time steps. For example, performing maintenance and/or purchasing equipment to fulfill cost incentive requirements can reduce the operational costs for consecutive time steps since additional maintenance has been performed on existing equipment and/or equipment has been replaced, both of which can reduce operational costs. Additionally, the equipment may operate at a higher efficiency after the maintenance and/or the replacement, thereby reducing operational costs. In some embodiments, some and/or all steps of process 1700 are performed by MPM system 602.

Process 1700 is shown to include receiving cost incentive information from a cost incentive service (step 1702), according to some embodiments. In some embodiments, the cost incentive service provides all cost incentives available to the cost incentive service. In some embodiments, the cost incentive service selects a subset of all cost incentives available to the cost incentive service, such that the subset includes only cost incentives relevant to building equipment. In some embodiments, the cost incentive information indicates that no cost incentives are available at a current time and/or in the future. In some embodiments, cost incentive service 838 and MPM system 602 perform some and/or all of step 1702.

Process 1700 is shown to include identifying cost incentives associated with maintenance and replacement of building equipment (step 1704), according to some embodiments. In some embodiments, step 1704 includes determining whether any cost incentives are available. If no cost incentives are available, process 1700 may include performing model predictive maintenance without account for any cost incentives. If cost incentives are available, the cost incentives indicated by the cost incentive information received in step 1702 can be divided into groups/subsets depending on whether the cost incentives are associated with maintenance and/or capital purchases. A cost incentive may require maintenance and one or more capital purchases in order to be fulfilled. In some embodiments, if a cost incentive requires both maintenance and one or more capital purchases to be fulfilled, the cost incentive is treated as a package of linked decisions. In some embodiments, if a cost incentive requires both maintenance and one or more capital purchases to be fulfilled, the cost incentive is linked to certain combinations of maintenance and purchase activities. For example, if a value of two binary decision variables is are true (i.e., 1) for two corresponding activities required to fulfill the cost incentive, a binary decision for the cost incentive may also be true (e.g., B_(tax)=B_(main)×B_(cap)) where 1 is true and 0 is false. As such, B_(tax)=1 may cause the cost revenue to be included during optimization of the objective function J. In some embodiments, if all requirements need to be met to obtain a cost savings from the cost incentive, each maintenance and/or capital purchase in each group/subset will only be performed if every other maintenance and/or capital purchase in each group/subset is also performed. In some embodiments, cost incentive manager 950 performs some and/or all of step 1704.

Process 1700 is shown to include determining a modified cost (Cost_(main,mod)) of performing maintenance on building equipment including one or more cost incentives associated with maintenance (step 1706), according to some embodiments. In some embodiments, if no cost incentives are available, the modified cost of performing maintenance on building equipment may be determined without accounting for any cost incentives. In some embodiments, if no cost incentives are available, step 1706 is skipped. In some embodiments, Cost_(main,mod) is calculated based on all maintenance activities performed at each time step in an optimization period. In some embodiments, maintenance cost predictor 920 performs some and/or all of step 1706.

Process 1700 is shown include determining a modified cost (Cost_(cap,mod)) of purchasing/replacing building equipment (i.e., capital purchases) including cost incentives associated with capital purchases (step 1708), according to some embodiments. In some embodiments, if no cost incentives are available, the modified cost of purchasing/replacing building equipment may be determined without accounting for any cost incentives. In some embodiments, if no cost incentives are available, step 1708 is skipped. In some embodiments, Cost_(cap,mod) is calculated based on all capital purchase activities performed at each time step in the optimization period. In some embodiments, capital cost predictor 930 performs some and/or all of step 1708.

Process 1700 is shown include performing a model predictive maintenance process with Cost_(main,mod) and Cost_(cap,mod) to determine an optimal equipment servicing strategy for the building equipment (step 1710), according to some embodiments. In some embodiments, step 1710 includes performing process 1000 described with reference to FIG. 10. In some embodiments, the optimal equipment servicing strategy includes an optimal maintenance strategy and an optimal capital purchase strategy. In some embodiments, the optimal equipment servicing strategy is used to optimize (i.e., minimize) combined costs over the optimization period. In some embodiments, MPM system 602 as described with reference to FIGS. 6-9 performs some and/or all of step 1710.

Model Predictive Maintenance of a Variable Refrigerant Flow System

Referring now to FIGS. 18A-18B, a variable refrigerant flow (VRF) system 1800 is shown, according to some embodiments. VRF system 1800 is shown to include a plurality of outdoor VRF units 1802 and a plurality of indoor VRF units 1804. Outdoor VRF units 1802 can be located outside a building and can operate to heat or cool a refrigerant. Outdoor VRF units 1802 can consume electricity to convert refrigerant between liquid, gas, and/or super-heated gas phases. Indoor VRF units 1804 can be distributed throughout various building zones within a building and can receive the heated or cooled refrigerant from outdoor VRF units 1802. Each indoor VRF unit 1804 can provide temperature control for the particular building zone in which the indoor VRF unit is located.

A primary advantage of VRF systems is that some indoor VRF units 1804 can operate in a cooling mode while other indoor VRF units 1804 operate in a heating mode. For example, each of outdoor VRF units 1802 and indoor VRF units 1804 can operate in a heating mode, a cooling mode, or an off mode. Each building zone can be controlled independently and can have different temperature setpoints. In some embodiments, each building has up to three outdoor VRF units 1802 located outside the building (e.g., on a rooftop) and up to 128 indoor VRF units 1804 distributed throughout the building (e.g., in various building zones).

Many different configurations exist for VRF system 1800. In some embodiments, VRF system 1800 is a two-pipe system in which each outdoor VRF unit 1802 connects to a single refrigerant return line and a single refrigerant outlet line. In a two-pipe system, all of the outdoor VRF units 1802 operate in the same mode since only one of a heated or chilled refrigerant can be provided via the single refrigerant outlet line. In other embodiments, VRF system 1800 is a three-pipe system in which each outdoor VRF unit 1802 connects to a refrigerant return line, a hot refrigerant outlet line, and a cold refrigerant outlet line. In a three-pipe system, both heating and cooling can be provided simultaneously via dual refrigerant outlet lines.

In some embodiments, VRF system 1800 is integrated with model predictive maintenance (MPM) system 602 described with reference to FIGS. 6-9. In some embodiments, MPM system 602 is configured to determine an optimal maintenance strategy for VRF system 1800 and any/all components therein. In some embodiments, MPM system 602 is configured to determine an optimal purchase/replacement strategy for VRF system 1800 and any/all components therein similar to and/or the same as the below.

In some embodiments, MPM system 602 is configured to monitor some and/or all of the components of VRF system 1800 for each component's current state of degradation and usage estimations (e.g., load predictions and performance curves). For example, MPM system 602 can monitor each of the indoor VRF units 1804 and each of the outdoor VRF units 1802. In some embodiments, each of the VRF units have a different current state of degradation due to various factors (e.g., when the VRF unit was installed, how often the VRF unit is used, what average level of power the VRF unit is run at, etc.). Based on the current state of degradation and usage estimations, MPM system 602 can predict operational costs, maintenance costs, and/or capital costs associated with equipment. In some embodiments, these predictions are made through a process similar to and/or the same as process 1000 described with reference to FIG. 10.

In some embodiments, after the various costs above are predicted, the objective function J is generated for an optimization period. After the objective function J is generated, MPM system 602 can be configured to optimize (i.e., minimize) the objective function J. In some embodiments, the optimization of the objective function J determines optimal values of decision variables for each of the components of VRF system 1800. For example, one decision variable may indicate that an indoor VRF unit 1804 will need to have maintenance performed on it at a particular time step during the optimization period in response to a building zone not being cooled properly. As another example, another decision variable may indicate that an outdoor VRF unit 1802 may need to be replaced (i.e., incurring a capital cost) at a particular time step in the optimization period in response to a detection that outdoor VRF unit 1802 is consuming an additional 50% more power than when the outdoor VRF unit 1802 was installed.

In some embodiments, one or more cost incentives are related to VRF system 1800 that allow MPM system 602 to further optimize the objective function J. For example, a cost incentive may provide a tax savings for replacing a current refrigerant with an eco-friendly refrigerant. When optimizing the objective function J, MPM system 602 can determine the tax savings for fulfilling the cost incentive may reduce total costs over the optimization period. In some embodiments, replacing the current refrigerant with the eco-friendly refrigerant incurs additional maintenance costs as the eco-friendly refrigerant will need to be purchased and replaced in VRF system 1800. In some embodiments, replacing the current refrigerant with the eco-friendly refrigerant provide the tax savings and additionally reduce operational costs. In some embodiments, cost incentives are implemented by a government to promote more efficient technology by offsetting some of an initial cost of implementing the cost incentives. As such, by implementing the eco-friendly refrigerant, VRF system 1800 may both acquire the tax savings and reduce operational costs over the optimization period.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures show a specific order of method steps, the order of the steps can differ from what is depicted. Also two or more steps can be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps. 

What is claimed is:
 1. A model predictive maintenance system for building equipment, the system comprising: processing circuitry configured to: operate the building equipment to affect a variable state or condition in a building; predict a cost of operating the building equipment over a duration of an optimization period; predict a cost of performing maintenance on the building equipment over the duration of the optimization period; determine whether any cost incentives are available; in response to a determination that one or more cost incentives are available, identify the one or more cost incentives associated with performing maintenance on the building equipment; optimize an objective function to predict a total cost associated with the building equipment over the duration of the optimization period, the objective function comprising the predicted cost of operating the building equipment and the predicted cost of performing maintenance on the building equipment, the objective function further comprising the one or more cost incentives associated with performing maintenance on the building equipment if the one or more cost incentives are available.
 2. The model predictive maintenance system of claim 1, wherein the processing circuitry is further configured to predict a cost of purchasing or replacing the building equipment over the duration of the optimization period, wherein the objective function further comprises the predicted cost of purchasing or replacing the building equipment.
 3. The model predictive maintenance system of claim 2, wherein the processing circuitry is further configured to determine one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.
 4. The model predictive maintenance system of claim 1, wherein the processing circuitry is further configured to dynamically update the objective function on a real-time basis based on closed-loop feedback from the building equipment.
 5. The model predictive maintenance system of claim 1, wherein the processing circuitry is configured to: identify a time period for each of the one or more cost incentives when each of the one or more cost incentives are available; and wherein the objective function further comprises the time period for each of the one or more cost incentives.
 6. The model predictive maintenance system of claim 1, wherein the one or more cost incentives each define one or more requirements to achieve the cost incentive.
 7. The model predictive maintenance system of claim 1, wherein the processing circuitry is further configured to: determine an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives; and optimize the objective function to determine whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith, wherein optimizing the objective function comprises minimizing the predicted total cost over the duration of the optimization period.
 8. A method for performing model predictive maintenance for building equipment, the method comprising: operating the building equipment to affect a variable state or condition in a building; predicting a cost of operating the building equipment over a duration of an optimization period; predicting a cost of performing maintenance on the building equipment over the duration of the optimization period; determining whether any cost incentives are available; in response to a determination that one or more cost incentives are available, identifying the one or more cost incentives associated with performing a maintenance on the building equipment; and optimizing an objective function to predict a total cost associated with the building equipment over the duration of the optimization period, the objective function comprising the predicted cost of operating the building equipment and the predicted cost of performing maintenance on the building equipment, the objective function further comprising the one or more cost incentives associated with performing maintenance on the building equipment if the one or more cost incentives are available.
 9. The method of claim 8, further comprising predicting a cost of purchasing or replacing the building equipment over the duration of the optimization period, wherein the objective function further comprises the predicted cost of purchasing or replacing the building equipment.
 10. The method of claim 9, further comprising determining one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.
 11. The method of claim 9, wherein optimizing the objective function further comprises minimizing the objective function to determine whether and when to perform each particular type of maintenance to minimize the total cost associated with the building equipment over the duration of the optimization period.
 12. The method of claim 8, wherein the one or more cost incentives each define one or more requirements to achieve the cost incentive.
 13. The method of claim 8, further comprising: determining an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives; and wherein optimizing the objective function further comprises: determining whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith; and minimizing the predicted total cost over the duration of the optimization period.
 14. A model predictive maintenance system for building equipment, the system comprising: processing circuitry configured to: operate the building equipment to affect a variable state or condition in a building; predict a cost of operating the building equipment over a duration of an optimization period; predict a cost of performing maintenance on the building equipment over the duration of the optimization period; determine whether any cost incentives are available; in response to a determination that one or more cost incentives are available, identify the one or more cost incentives associated with performing maintenance on the building equipment; and optimize an objective function to determine an optimal strategy for operating and maintaining the building equipment over the duration of the optimization period, the objective function comprising the predicted cost of operating the building equipment and the predicted cost of performing maintenance on the building equipment, the objective function further comprising the one or more cost incentives associated with performing maintenance on the building equipment if the one or more cost incentives are available.
 15. The model predictive maintenance system of claim 14, wherein the processing circuitry is further configured to predict a cost of purchasing or replacing the building equipment over the duration of the optimization period, wherein the objective function further comprises the predicted cost of purchasing or replacing the building equipment.
 16. The model predictive maintenance system of claim 15, wherein the processing circuitry is configured to determine one or more cost incentives associated with purchasing or replacing one or more devices of the building equipment.
 17. The model predictive maintenance system of claim 14, wherein the processing circuitry is further configured to dynamically update the objective function on a real-time basis based on closed-loop feedback from the building equipment.
 18. The model predictive maintenance system of claim 14, wherein the processing circuitry is configured to: identify a time period for each of the one or more cost incentives when each of the one or more cost incentives are available; and wherein the objective function further comprises the time period for each of the one or more cost incentives.
 19. The model predictive maintenance system of claim 14, wherein the one or more cost incentives each define one or more requirements to achieve the cost incentive.
 20. The model predictive maintenance system of claim 14, wherein the processing circuitry is further configured to: determine an amount of revenue and a particular maintenance activity associated with each of the one or more cost incentives; and optimize the objective function to determine whether and when each particular maintenance activity should be performed during the optimization period to achieve the amount of revenue associated therewith, wherein optimizing the objective function comprises minimizing a predicted total cost over the duration of the optimization period. 